-
Notifications
You must be signed in to change notification settings - Fork 31
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
update to controller-runtime 0.18.3 #380
Conversation
Skipping CI for Draft Pull Request. |
/test all |
8e07698
to
1566809
Compare
/test all |
1566809
to
2bd800b
Compare
/test all |
2bd800b
to
0bfa35d
Compare
/test all |
fddc5e8
to
89f2eaa
Compare
/test all |
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.
/approve
LGTM label has been added. Git tree hash: db63db8b1af571ce60a78261e9030e9656b2e0ef
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: embik The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
This bumps controller-runtime to 0.18 and takes the opportunity to clean up the OSP bootstrapping.
Previously, the default OSPs were reconciled once on OSM startup by watching Deployment creation in the
kube-system
namespace in the worker cluster.The new code uses a channel to trigger the initial reconciliation in empty clusters. The original OSP controller would revert any OSP updates back to the version compiled into OSM, but only when a) OSM is restarted or b) a Deployment is created. So the controller is in fact reconciling like most other controllers and so is now also simply watching OSPs to reconcile unwanted changes immediately.
The reconciler also removes the ResourceVersion/Generation setting by simply not overwriting the entire OSP object (including metadata), but only overwriting its Spec when reconciling.
I also removed the duplicated OSP map (the default OSPs were both embedded and kept as a duplicate in
defaultOSPFiles
) and instead parse the OSPs once upon startup and keep those objects around. The controller will now in general reconcile a little bit more than before, so not having to re-parse the YAML everytime should compensate for the additional reconcilings.What type of PR is this?
/kind cleanup
/kind chore
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: