-
Notifications
You must be signed in to change notification settings - Fork 98
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
Bump ControllerGen, CRD #1598
Bump ControllerGen, CRD #1598
Conversation
@k0da CRD change, I would appreciate extra pair of eyes in review here, thanks :) |
@kuritka do we really need to change CRD? |
@k0da , good question. Not IMO although upgrade tests pass. Curretly CRD is ochanged by controller-gen (in our case automatically when |
Signed-off-by: Michal Kuritka <kuritka@gmail.com>
@@ -77,26 +83,31 @@ spec: | |||
- kind | |||
- name | |||
type: object | |||
x-kubernetes-map-type: atomic |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Applicable to maps. atomic means that the map can only be entirely replaced by a single manager. granular means that the map supports separate managers updating individual fields.
Looks matching our case
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've double-checked the CRD changes, see inline comments. Looks safe to upgrade to me.
kind: "" | ||
plural: "" | ||
conditions: [] | ||
storedVersions: [] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like a fix for kubernetes-sigs/controller-tools#456 , good to proceed 👍
@@ -77,26 +83,31 @@ spec: | |||
- kind | |||
- name | |||
type: object | |||
x-kubernetes-map-type: atomic |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Applicable to maps. atomic means that the map can only be entirely replaced by a single manager. granular means that the map supports separate managers updating individual fields.
Looks matching our case
I'm upgrading the kube-linter to the latest version. I need to do this before I bump the depenencies in the go.mod files. This change modifies the CRD!
..
HOW TO RUN CI
---By default, all the checks will be run automatically. Furthermore, when changing website-related stuff, the preview will be generated by the netlify bot.
Heavy tests
Add the
heavy-tests
label on this PR if you want full-blown tests that include more than 2-cluster scenarios.Debug tests
If the test suite is failing for you, you may want to try triggering
Re-run all jobs
(top right) with debug logging enabled. It will also make the print debug action more verbose.