-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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 Cilium to 1.7 for k8s 1.12+ #8589
Conversation
Hi @olemarkus. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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/test-infra repository. |
/ok-to-test |
/lgtm |
- create | ||
- get | ||
- list | ||
- watch |
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.
Won't removing this adversely affect version 1.6?
Yes you may be right there. I'll add it back in |
8dc28e0
to
e410dde
Compare
You could put a version conditional in the template. |
Cilium 1.7 requires K8s 1.12 minimum. Changed the templates so that we can have different cilium versions for different k8s versions. This also mean that this addon will behave similar to other addons wrt upgrades. Cilium used to add a fixed version to the cluster spec on cluster creation so upgrades were slightly more manual. Now, for new clusters, upgrades will happen implicitly with kops updates unless the .Version is added manually to the cluster spec.
e410dde
to
d0d8331
Compare
I would if this was more security sensitive. But this particular change is basically just about dropping the deprecated k8s extensions apis. |
@@ -593,9 +593,6 @@ func (c *Cluster) FillDefaults() error { | |||
} else if c.Spec.Networking.AmazonVPC != nil { | |||
// OK | |||
} else if c.Spec.Networking.Cilium != nil { | |||
if c.Spec.Networking.Cilium.Version == "" { | |||
c.Spec.Networking.Cilium.Version = CiliumDefaultVersion |
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.
Instead of baking the logic in the templates, this could have picked the default version by doing check on the Kubernetes version. That would allow other Go code to do Cilium version checks. But we don't have any such Cilium version checks, so not a blocker.
/lgtm |
version := "1.6.6-kops.0" | ||
version := "1.7.0-kops.1" |
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.
Maybe use something like this here?
kops/upup/pkg/fi/cloudup/bootstrapchannelbuilder.go
Lines 861 to 866 in 91867ce
versions := map[string]string{ | |
"k8s-1.8": "1.5.0-kops.1", | |
"k8s-1.10": "1.5.0-kops.2", | |
"k8s-1.12": "1.5.5-kops.1", | |
"k8s-1.16": "1.6.0-kops.1", | |
} |
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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: olemarkus, 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 |
Seems that e2e for Cilium is failing after this change. @olemarkus any thoughts?
My guess is that it's the extra kops/upup/models/cloudup/resources/addons/networking.cilium.io/k8s-1.12.yaml.template Line 402 in ea8c8fb
|
Yep. I'll have a PR momentarily |
…for k8s 1.12+ kubernetes#8591: Fix typo in the cilium default version"
Cilium 1.7 requires K8s 1.12 minimum. Changed the templates so that we
can have different cilium versions for different k8s versions.
This also mean that this addon will behave similar to other addons wrt
upgrades. Cilium used to add a fixed version to the cluster spec on cluster creation so
upgrades were slightly more manual. Now, for new clusters, upgrades will
happen implicitly with kops updates unless the .Version is added
manually to the cluster spec.