-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Add fixed version to all addons #12416
Conversation
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.
Can you set Version as KopsVersion? Should be good enough for what we want upgraded and won't be a strange fixed number.
@@ -105,6 +105,11 @@ func (b *BootstrapChannelBuilder) Build(c *fi.ModelBuilderContext) error { | |||
} | |||
|
|||
for _, a := range addons.Spec.Addons { | |||
// Older versions of channels that may be running on the upgrading cluster requires Version to be set | |||
// We hardcode version to a high version to ensure an update is triggered on first run, and from then on | |||
// only a hash change will trigger an addon update. |
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.
Consider mentioning "This can be removed when kops no longer supports k8s 1.22"
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.
Unfortunately this follows kops versioning and we don't have any skew/upgrade jump policy. This will have to remain forever unless we change this
We need to set a version that is at least as high as the old addon versions. That is 4.0.0, I think. If we don't none of these addons will be updated. |
My understanding is that they will be updated once new control-plane nodes are started, we just need the kOps ones (like kops-controller) to be updated before that. |
This will make also older channels trigger addon updates
This will prevent an old kops-controller pod from being scheduled to the new master.
35bf523
to
d1ff109
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rifelpet 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 |
…416-origin-release-1.22 Automated cherry pick of #12416: Add fixed version to all addons
This should ensure addon updates are triggered before rolling the cluster, as expected.
We also update addons before labeling masters to ensure that kops-controller is updated before it is scheduled.
Should hopefully fix #12249
/cc @zetaab