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

Feature Request: add stages to fix concurrency/dependency issues #4701

Closed
baptiste-bonnaudet opened this issue Sep 26, 2018 · 2 comments
Closed
Labels

Comments

@baptiste-bonnaudet
Copy link

Hi,

At the moment Helm acts similarly to a kubectl apply and all templates are pushed to the k8s api as they come.

It adds lots of complexity when resources depends on one another or when interacting with an external service (like GCP service broker for K8S).

I'd love to see a feature that would add stages to a helm install/upgrade to give the chart developer more flexibility and avoid workaround for race conditions.

Cheers

@krish7919
Copy link

krish7919 commented Nov 23, 2018

Is there a roadmap for this? Or will this not be done?

In my mind, is it as simple as adding a priority label in the resources and helm can submit it as per the ascending order of priority?

@bacongobbler
Copy link
Member

closing as inactive.

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

No branches or pull requests

4 participants