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 disabling openapi validations for CRD upgrades #16144

Open
oavner opened this issue Oct 29, 2023 · 1 comment
Open

Support disabling openapi validations for CRD upgrades #16144

oavner opened this issue Oct 29, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@oavner
Copy link

oavner commented Oct 29, 2023

Summary

managing crds is a big pain for any operator developer so some choose to manage CRDs via helm hooks (nvidia's gpu-operator for example). when upgrading a chart version one might deploy a CR of a new CRD that is yet to be upgraded. It this case the said helm hook wouldn't run and the CRs of the said CRD would not be upgraded because of failed openapi validations. We need a way to disable these openapi validations in order to upgrade CRDs via helm hooks first and only then deploy the CRs of the new CRD version.

Motivation

see this issue opened for nvidia gpu-operator and their documentation .

also see related PR and issue to helm about openapi validations.

Proposal

Add options to the helm spec of the argo application so we could add custom helm options to installation / upgrade / sync procedures.

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

No branches or pull requests

2 participants