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

Support CRD and CR ordering #553

Open
huyhg opened this issue Mar 6, 2021 · 1 comment
Open

Support CRD and CR ordering #553

huyhg opened this issue Mar 6, 2021 · 1 comment

Comments

@huyhg
Copy link
Contributor

huyhg commented Mar 6, 2021

Fully supporting the helm client is definitely a way to fix this, since helm handles CRDs. We can also consider one of the following fixes:

  • We do two kubectl apply's. The first one only applies CRDs. The second one applies the rest.
  • Switch from using kubectl apply to kpt live apply. The latter properly handles resource ordering. However, its behavior is also different from kubectl apply, such as waiting for all resources to reconcile, so this is a higher risk change. It's also not immediately clear to me how to control its version compatibility.
@maelvls
Copy link

maelvls commented Jun 21, 2021

Note that Helm does not handle CRD upgrades. But AFAIK the Marketplace's "deployer" mechanism only works for day-1 installations, not for day-2 operations like application upgrades.

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

No branches or pull requests

2 participants