Config to define mapping between k8s namespace and service registry namespace

[arnatal]

Currently, the Operator takes the name of the namespace in k8s and uses it as the namespace for the service registry. It might be interesting to have a configuration option that would allow to specify which k8s namespace maps to which service registry namespace.

[asimpleidea]

I had a stub about this some time ago but haven't implement it yet. It was based on overrides:

• if you annotate a namespace/service/whatever with operator.cnwan.io/name: another-name, the operator will override its name
• same thing for operator.cnwan.io/region: eu for regions for those that support it

And so on.

The hardest part is probably going to be deletion of the resource or removal of the annotation, which will probably involve the creation of smarter controllers.

[arnatal]

Ah I see what you mean. What I had in mind was more along the lines of proving the name mapping as part of the Operator YAML settings. Using settings.yaml might be easier to implement/configure but your proposal seems more scalable, so I'm not sure what's best.