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

Add install order #10

Closed
tylerauerbeck opened this issue Dec 31, 2020 · 4 comments
Closed

Add install order #10

tylerauerbeck opened this issue Dec 31, 2020 · 4 comments

Comments

@tylerauerbeck
Copy link
Contributor

Occasionally the helm install will fail because the CheCluster is applied before the CRD is available. Need to update the chart to be smart enough to apply in the appropriate order.

@jtudelag
Copy link
Contributor

jtudelag commented Jan 7, 2021

Hey @tylerauerbeck , I got hit by his 100% of the times I have tried to install the chart ...
Not sure why, never got it right. Also it is quite hard to debug this because the dry-run does not work due to the "lookup" function...

I haven't found a way to specify the order in which manifest are rendered/process...
I will propose to separate this in two charts, install any operator first, and then the rest of the content as suggested here: https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#install-a-crd-declaration-before-using-the-resource

Thoughts?

@tylerauerbeck
Copy link
Contributor Author

@jtudelag I think that's the route to go for right now (and then just have two seperate helm install commands). There are a few other ideas I'm working on right now, but will need some time to prove them out.

@tylerauerbeck
Copy link
Contributor Author

@jtudelag Actually I came up with a way to use post-install hooks to get this working. I'll PR this here shortly and then we should be good to go.

@tylerauerbeck
Copy link
Contributor Author

Handled in #19

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

Successfully merging a pull request may close this issue.

2 participants