-
Notifications
You must be signed in to change notification settings - Fork 218
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
Support chart installation to an existing namespace #34
Comments
The tool purposely installs charts into newly created namespaces that are deleted afterwards. If you don't want this why don't you just |
@unguiculus that's what I'm doing right now, however that means that I'm also separately implementing functionality around git diffs and picking up on values files in the I realize that chart-testing originated just to suit the requirements of helm/charts, but enabling the use of namespaced privileges as described here would allow many more teams to leverage the library. |
Ah, I do see now that |
v2.0.0 is all written in Go. 😄 |
Now that |
@unguiculus If I understand what you're saying, it's that someone who needs to install in an existing namespace should create a script that...
I know we have some lessons learned from these that others may not have, too. For example, the way we wait for deployments in addition to helm waiting. Would it be better to implement it here, for someone else to come up with a tool that does it, or others to do it as they need? |
This PR adds two flags to the `install` command: `namespace` and `release-label`. If `namespace` is specified, releases will target that namespace and `release-label` will be used to select deployments and pods for readiness and reading log output. Fixes #34
I am working with an organization that runs a dedicated tiller instance for each set of namespaces owned by a given business unit. None of these tiller instances have cluster-admin permissions, nor can they create/delete arbitrary namespaces. Teams may also maintain their own chart repositories.
Specifying an existing namespace for chart installation would allow teams to consume this library in a more distributed and self-service manner, without the need for a dedicated cluster or access to a more highly privileged tiller instance.
The text was updated successfully, but these errors were encountered: