You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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
/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 commandkops version
, will displaythis information.
Version 1.23.4 (git-824158f51fcf68a7fb2af36cd765034d5023f425)
2. What Kubernetes version are you running?
kubectl version
will print theversion 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:
Please see:
projectcalico/calico#5011
projectcalico/calico#5717
Workaround:
Update your cluster.yaml with an updated version of Calico
The text was updated successfully, but these errors were encountered: