-
Notifications
You must be signed in to change notification settings - Fork 564
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
Ordering #137
Comments
not currently |
@Stono Hi! Just curious but why do you want the ordering? |
Hello @mumoshu! We have a helmfile which can take an empty kubernetes cluster and turn it into what we call the "delivery platform", however the components need to be deployed in a certain order, for a variety of reasons:
As a result, we've ended up with a bit of a hacky script that looks like this:
|
@Stono Hi. Thank you so much for the detailed explanation! Btw, would this suggested feature #151 (comment) help your use-case, too? |
Yes it would so long as the files were processed in order 👌
…On Fri, 25 May 2018, 8:30 am KUOKA Yusuke, ***@***.***> wrote:
@Stono <https://github.com/Stono> Hi. Thank you so much for the detailed
explanation!
Makes sense.
Btw, would this suggested feature #151 (comment)
<#151 (comment)>
help your use-case, too?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#137 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABaviRcqT5qDyVTJxY9m4HSUjtGLu8vQks5t17MWgaJpZM4T5faL>
.
|
To throw in another usage case, we have Helm charts for Roles and RoleBindings. IIRC, the latter will fail if you try to bind a Role that doesn't exist yet. We also Chart StorageClasses, which have to be the very first thing provisioned (our default storage class, in particular). |
@gtaylor what's the logic for having roles and rolebindings in separate charts and not in the same chart? |
You don't always need both. |
I don't understand why you would have roles, but not bind them to anything. Seems like they go together to me and I would also enable/disable them through flags instead of having them in separate charts, but I don't have your full use-case. |
We create roles on clusters for specific user types at the point of cluster bootstrapping, ClusterRoleBindings are added at a later date. Roles and RoleBindings don't need to go in separate charts however, I believe you can do a rolebinding to a non-existent role and k8 just resolves them later when the role exists. |
#247 would allow more granular control over ordering. |
@mumoshu looked at the docs but not 100% sure how ordering works. Can I just do this and they will be installed in the order that they are specified?
|
Nope. Releases are handled concurrently per |
Thus basically you can achieve some ordering by setting concurrency to 1 :) But probably it's better to do something like this:
|
@andrewnazarov Thanks for the comment! Yeah I think that's correct. Also see #715 that will give you concurrency AND ordering without splitting helmfile.yaml files. |
Signed-off-by: yxxhero <aiopsclub@163.com>
For those here today, you can use |
Firstly,
Thanks for this project, it's awesome - you've saved me a big headache.
However, quick Q. I need to control the order in which the charts are deployed.
Is there any way (hacky or not) that I can do that, without using labels and having two helmfile runs?
The text was updated successfully, but these errors were encountered: