I have been influenced recently by the recent position of the ArgoCD project that establishing an opinionated baseline on how secrets should be managed is in the best interest of kubernetes users, see https://blog.argoproj.io/announcing-argo-cd-v3-small-but-mighty-df05c0b39ad6
It seems reasonable that handling secrets in a robust way in Orange Lab would benefit from pre-installing external-secrets operator during provisioning. The use case I have for this is for cases when sharing services with semi or untrusted services and external cloud services is important, it would allow users more advanced capabilities out of the box for very little cost in terms of resource consumption, and prevent footguns from the mess of options that exist with secret injections.
If this is a good idea I could make a PR to implement it as an optional install parameter.
I have been influenced recently by the recent position of the ArgoCD project that establishing an opinionated baseline on how secrets should be managed is in the best interest of kubernetes users, see https://blog.argoproj.io/announcing-argo-cd-v3-small-but-mighty-df05c0b39ad6
It seems reasonable that handling secrets in a robust way in Orange Lab would benefit from pre-installing external-secrets operator during provisioning. The use case I have for this is for cases when sharing services with semi or untrusted services and external cloud services is important, it would allow users more advanced capabilities out of the box for very little cost in terms of resource consumption, and prevent footguns from the mess of options that exist with secret injections.
If this is a good idea I could make a PR to implement it as an optional install parameter.