Prune Sebastien THOMAS

Thanks for quick answer. I actually cloned the `kubecolor` project into a new repo and applied a ton of patches, so I guess the output now changed slightly: https://github.com/kubecolor/kubecolor I...

this patch was applied at https://github.com/kubecolor/kubecolor

any idea how to get the data from a remote URL instead of a file ?

This is fixed in the new clone of the project. Get it at https://github.com/kubecolor/kubecolor or brew install kubecolor/tap/kubecolor

Actually, the foolproof functions you are mentioning could already do the trick and should be able to detect if either : - an operator is already running in the same...

in Cert-Manager for example, they are using : ``` "k8s.io/client-go/tools/leaderelection" "k8s.io/client-go/tools/leaderelection/resourcelock" ``` Which is instanciated at https://github.com/jetstack/cert-manager/blob/5f96b378e6a8bc99e63d011cd5d33d4999d1e21c/cmd/controller/app/controller.go#L104 and https://github.com/jetstack/cert-manager/blob/5f96b378e6a8bc99e63d011cd5d33d4999d1e21c/cmd/controller/app/controller.go#L210 I'll check in other operators (and in Operator SDK, but I...

Well, my suggestion would be to lock in the namespace where the first operator is started. But most of the time, you will die if you have 2 namespace-scope operator...

The limitation is that you don't have the choice to where you put the operator. All my cluster-scoped operators and services are in a `tools` namespace (kafka-operator, prometheus-operator, etcd-operator, elasticsearch-operator,...

@SidGrundfos the Operator is here to create Nats clusters, and is not a Nats server/cluster on its own. Once installed, you can create a cluster in the namespace you want...

Well, I have no experience with Nats streaming operator. I see one of the pods is loop-crashing... why ? Ensure your nats clusters (nats + streaming) are working, test it...