Aidan Shribman

@sa-cloud - can you provide some examples for **presents** being used in official (which exists in the respective public hubs) helm and operator implementation?

The Operator can be added in 3 phases: - helm operator (based on https://github.com/skydive-project/skydive/pull/1963) - ansible operator - go operator

> I finally found time to convert the HELM charts to a HELM based operator. I created a directory called operator under the contrib folder. I will create a PR...

# Templating ## by resources under namespace ``` G.V().Has("K8s.Namespace", "@1") @1 --> G.V().Values("K8s.Namespace") ``` ## by k8s resouces under namespace ``` G.V().Has("Manager", "k8s").Has("K8s.Namespace", "@1") @1 --> G.V().Has("Manager", "k8s").Values("K8s.Namespace") ``` ##...

# AND operator ## services under kube-system ``` G.V() *AND* Has("K8s.Namespace", "kube-system") *AND* Has("Type", "service") G.V() .Has("K8s.Namespace", "kube-system") .Has("Type", "service") ```

## OR operator # kube-system or istio-system ``` G.V().Has("K8s.Namespace", "kube-system") *OR* G.V().Has("K8s.Namespace", "istio-system") G.V().Has("K8s.Namespace", "kube-system").As("1") .G.V().Has("K8s.Namespace", "istio-system").As("2") .Select("1", "2") ```

So do we want to change ShortestPathTo() or add a new gremlin step ?

ok ... any guidance in case I want to attempt to extend it myself ?

@RobertJBarron - does the above provide a reasonable solution? if so then please close issue