Kubernetes controller for multi-tenancy. It propagates resources between namespaces accurately and allows tenant users to create/delete sub-namespaces.
Currently, Accurate does not allow tenant users to set new labels/annotations to sub-namespaces created from SubNamespace objects.
It is handy to allow tenant users to set new labels/annotations only when:
the label/annotation key is included in the configuration file, and
the label/annotation is not set for the parent namespace.
How
Add new fields to SubNamespace, for example, spec.labels and spec.annotations
Enhance accurate-controller to create a sub-namespace with the specified labels/annotations.
accurate-controller has to ignore labels/annotations whose key is not listed in the configuration file.
It also should not set labels/annotations if the same labels/annotations are set for the parent namespace.
Nevertheless, the value would be overwritten by the existing Namespace controller to the value of the parent labels/annotations.
What
Currently, Accurate does not allow tenant users to set new labels/annotations to sub-namespaces created from SubNamespace objects.
It is handy to allow tenant users to set new labels/annotations only when:
How
spec.labels
andspec.annotations
accurate-controller
to create a sub-namespace with the specified labels/annotations.accurate-controller
has to ignore labels/annotations whose key is not listed in the configuration file.It also should not set labels/annotations if the same labels/annotations are set for the parent namespace. Nevertheless, the value would be overwritten by the existing Namespace controller to the value of the parent labels/annotations.
Describe how to address the issue.
Checklist