Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document large cluster workflow for operator deployment involving multiple teams #120

Open
nfnt opened this issue Dec 16, 2019 · 1 comment
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@nfnt
Copy link
Member

nfnt commented Dec 16, 2019

What would you like to be added:
With the help of kudo install --skip-instance, only the Operator and OperatorVersion of a package can be installed. This can be used in larger cluster by cluster ops teams preparing operators for other teams. I.e., this allows a workflow where specific teams are allowed to create instances from OperatorVersions already in the cluster, giving cluster ops more control on what is being deployed on a cluster.

Why is this needed:
KUDO's support for this workflow helps in large cluster deployments managed by multiple teams with different roles.

@nfnt nfnt added the documentation Improvements or additions to documentation label Dec 16, 2019
@kensipe
Copy link
Member

kensipe commented Mar 13, 2020

@nfnt could we get more feedback on this... it seems like a good idea in general but it also feels like it may be early. We likely need details around rbac and security to support this. thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants