You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for this promising project ! I was thinking of developing such an operator to suit my multi-tenancy needs, but this new one seems really good 😺
I'd love to be an early adopter of this project (even for some little production use cases), but I need to customize the default policy to an empty string.
Would it be possible to handle some environment variable, for example ? Thus, I'd be able to configure it directly in the operator Deployment spec using Helm.
Thanks !
The text was updated successfully, but these errors were encountered:
Thanks for this promising project ! I was thinking of developing such an operator to suit my multi-tenancy needs, but this new one seems really good 😺
I'd love to be an early adopter of this project (even for some little production use cases), but I need to customize the default policy to an empty string.
Would it be possible to handle some environment variable, for example ? Thus, I'd be able to configure it directly in the operator Deployment spec using Helm.
Thanks !
Hi Léo! Happy to hear that u like the project :)
I will look into it, but shouldn't be a difficult thing to implement, since policy.default is stored in internal/controller/common/defaults.go as a String.
You can fork and open a PR if u want to add this feature, otherwise I could look into it, and add it later on :D
looked into it, the default policy is not being set by the operator, since it's just adds policies to an already existing cm, if the CM does not exist, no policies will be created
I could add a CM to the Helm chart, but it will overwrite an already existing CM, thus deleting already existing policies
Argo CD offers a helm chart, maybe it's something u can look into or just change the default policy manually :)
Hi,
Thanks for this promising project ! I was thinking of developing such an operator to suit my multi-tenancy needs, but this new one seems really good 😺
I'd love to be an early adopter of this project (even for some little production use cases), but I need to customize the default policy to an empty string.
Would it be possible to handle some environment variable, for example ? Thus, I'd be able to configure it directly in the operator Deployment spec using Helm.
Thanks !
The text was updated successfully, but these errors were encountered: