Closed bergerx closed 4 years ago
@bergerx this project is open for contribution and should be able to run on any Kubernetes cluster. I recently made a change to make sure that happened. That said, Kubernetes does not seem to have the concept of user and groups, so I didn't know how to map those functionalities on kube. For now they are disabled. Any design/implementation suggestions here would be welcome.
To answer your other questions: yes, we have several users mostly in the OpenShift space (including users that use this in production), and you are right we have reached a level of adoption for this project where we should start publishing release notes.
As far as the CRD maturity, I wanted to see the reactions after this breaking change. maybe we are getting to the point where we can promote it to v1beta1, but I am not sure yet.
Thanks for the information, thats quite helpful.
Hi, this morning i've played a bit with the operator and so far this one is the closest tool that we currently need, we'd like to use and contribute to the project rather than creating an internal tool from scratch, but I have some open questions in mind:
NamespaceConfig.spec.resources
and v0.2.0 now has that field removed and replaced withNamespaceConfig.spec.templates.objectTemplate
, quite a big structural change in the crd.Also it would be helpful if you include such information into the readme.