Skip to content
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 Default Calico Version for Kubernetes 1.23 to 3.22.4 #14363

Closed
xgt001 opened this issue Oct 1, 2022 · 2 comments
Closed

Bump Default Calico Version for Kubernetes 1.23 to 3.22.4 #14363

xgt001 opened this issue Oct 1, 2022 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/office-hours

Comments

@xgt001
Copy link

xgt001 commented Oct 1, 2022

/kind bug

KOPS ships version 3.21.4 of Calico CNI by default in kops 1.23.4 for Kubernetes. Calico doesn't support ipset protocol 7 introduced in Kubernetes 1.23 until version 3.22.4. This causes the master's to be never validated if you use Calico CNI from KOPS and the downgrade path before you realise you need to update the version on Calico is quite harrowing :(

1. What kops version are you running? The command kops version, will display
this information.

Version 1.23.4 (git-824158f51fcf68a7fb2af36cd765034d5023f425)

2. What Kubernetes version are you running? kubectl version will print the
version if a cluster is running or provide the Kubernetes version specified as
a kops flag.

v1.23.12

3. What cloud provider are you using?
AWS

4. What commands did you run? What is the simplest way to reproduce this issue?
Tried upgrading from Kubernetes 1.22 to 1.23 with the following commands:

kops replace -f cluster.yaml --state $KOPS_STATE_STORE
kops update cluster $K8S_CLUSTER --target terraform --out 1.23-terraform-config/ --state $KOPS_STATE_STORE
cd 1.23-terraform-config/ ; terraform init; terraform plan; terraform apply
kops rolling-update --state $KOPS_STATE_STORE cluster --instance-group node-group --yes

Please see:
projectcalico/calico#5011
projectcalico/calico#5717

Workaround:
Update your cluster.yaml with an updated version of Calico

  networking:
    calico:
      version: v3.22.4
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Oct 1, 2022
@xgt001
Copy link
Author

xgt001 commented Oct 12, 2022

I see that this has been changed in the later versions of Kops (atleast 1.24.1)
However, we did get bitten when we used non-corresponding versions of Kops and we are very wary to use a later version of kops with an older version of kubernetes
Case in point: upgrading from 1.20 -> 1.21 broke with kops 1.24 broke because of the forced mount changes from /var/srv/kubernetes
Please let me know what you feel about backporting this change

@olemarkus
Copy link
Member

Please see https://kops.sigs.k8s.io/welcome/releases/
We do not support kOps 1.23 anymore.

@xgt001 xgt001 closed this as completed Oct 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/office-hours
Projects
None yet
Development

No branches or pull requests

4 participants