-
Notifications
You must be signed in to change notification settings - Fork 153
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
Improve the upgrade json patch mechanism #3248
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
dbe5dd8
to
8e97220
Compare
Improve the upgrade json patch by: 1. move it to its own package 2. made some refactoring for better performance 3. move the initialization of the upgradePatch object to boot, instead of in the reconcile loop, in order to fail fast on error 4. To implement 3, add a json string of the HyperConverged CR with default values. 5. To implement 4, add a tiny tool to go-generate the go file with the json string, and call it at build time Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
The CRDRemover type was written to remove the v2v CRDs on upgrade. This is no longer relevant. Even for newer CRD removes, we have a common solution - the json patch mechanism. This PR removes the unused code. Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
This API version is very old, and there is no need to remove it anymore. Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
8e97220
to
89beed8
Compare
Quality Gate passedIssues Measures |
Pull Request Test Coverage Report for Build 12504775034Details
💛 - Coveralls |
hco-e2e-upgrade-operator-sdk-aws lane succeeded. |
@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-upgrade-operator-sdk-azure In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
hco-e2e-upgrade-operator-sdk-sno-aws lane succeeded. |
@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-upgrade-operator-sdk-sno-azure In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
hco-e2e-operator-sdk-gcp, hco-e2e-operator-sdk-aws lanes succeeded. |
@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-operator-sdk-azure, ci/prow/hco-e2e-operator-sdk-sno-aws In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
hco-e2e-consecutive-operator-sdk-upgrades-aws lane succeeded. |
@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-consecutive-operator-sdk-upgrades-azure In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@nunnatsa: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
What this PR does / why we need it:
Improve the upgrade json patch by
Remove two old upgrade mechanism:
Reviewer Checklist
Jira Ticket:
Release note: