Closed anton-johansson closed 3 years ago
@anton-johansson awesome work. Everything looks good to me. There is a CI build error though. I'll check it out. Regarding containerd and runc, lets keep current versions for now.
Sounds good! Build is now fixed. Let me perform some real-cluster tests before we proceed here.
I'm actually not backing up my etcd yet, and since this PR involves a version-bump of etcd, this is a perfect opportunity to fix that first. :) So it might take some time before I can resume this.
If you (or anyone else) need 1.17 before I can resume, feel free to take over!
Closing in favor of #71.
NOTE: Not fully tested. Do not merge.
Kubernetes changelog can be found here: https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.17.md
Version bumps other than Kubernetes ones
etcd
etcd was bumped from
3.3.15
to3.4.3
, because this was found in the changelog:An upgrade from 3.3 to 3.4 should be zero-downtime using a regular rolling upgrade, according to their own documentation: https://etcd.io/docs/v3.3.12/upgrades/upgrade_3_4/
CNI plugins
The CNI plugins was bumped from 0.7.5 to 0.8.6, because this was found in this changelog:
Note that this bump was performed in Kubernetes 1.17.7, but since we're bumping to 1.17.9, this feels very appropriate. :)
Other
I don't see anything related to
runc
orcontainerd
- however - we probably never see that in their changelog since there are different container runtimes. But the current versions ofcontainerd
andrunc
that we use are both released after Kubernetes 1.17, so I think we can leave these as is for now, and maybe revisit this for the 1.18 bump. Or what do you think @amimof?Breaking changes
I could not find any breaking changes or deprecations regarding the command line parameters to the various services (
kube-apiserver
etc).