The namespace-configuration-operator helps keeping configurations related to Users, Groups and Namespaces aligned with one of more policies specified as a CRs
Hi, Thanks for sharing the great project. I have hundreds of personal namespaces for each employees in my company internal cluster.
I'm planning to use NamespaceConfig to setup pre-defined resources for them. But, I noticed LockedResource.templateObject uses very vanilla golang's text/template package (in operator-utils).
As mentioned in redhat-cop/operator-utils#35, redhat-cop/operator-utils#34 is supporting sprig functions an more (helm functions e.g. toYaml, etc.). Once the PR is released, it should upgrade to it.
Hi, Thanks for sharing the great project. I have hundreds of personal namespaces for each employees in my company internal cluster.
I'm planning to use
NamespaceConfig
to setup pre-defined resources for them. But, I noticedLockedResource.templateObject
uses very vanilla golang'stext/template
package (in operator-utils).https://github.com/redhat-cop/operator-utils/blob/master/pkg/util/lockedresourcecontroller/lockedresource/locked-resource.go#L69-L106
Vanilla
text/template
library doesn't support useful/complex functions. As a result, this doesn't allow to generate complex template processing.For example(from my usecase):
I would like to propose supporting sprig in processing
objectTemplate
.Note: I will post a PR to support this.