Update to Kubernetes v1.10 #70
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
April 6, 2018 15:45
Despite using `rootfsPropagation` after updating to Kubernetes v1.10 (not done
here yet) we are seeing:
RunContainerError: failed to start container 4ea4bde9b43a9eb241a5d7d98abf87184938f85ce9139949a3a246b6fe6b8985":
Error response from daemon:
linux mounts: path /etc/kubernetes/pki/etcd is mounted on /etc/kubernetes but it is not a shared or slave mount
Workaround this by temporarily (re)doing it in the entrypoint.
Signed-off-by: Ian Campbell <ijc@docker.com>
This also required updating some image versions in the caches:
kube_dns_version: 1.14.7 → 1.14.8
pause_version: 3.0 → 3.1
etcd_version: 3.1.11 → 3.1.12
From https://kubernetes.io/docs/imported/release/notes/#before-upgrading:
[action-required] The Container Runtime Interface (CRI) version has increased from v1alpha1 to v1alpha2.
Runtimes implementing the CRI will need to update to the new version, which configures container
namespaces using an enumeration rather than booleans. (#58973, @verb)
Thus we must update to a newer cri-containerd in lock-step. However this is
made more complicated because cri-containerd is no longer a standalone daemon
but has become a containerd plugin, which will require some rearchitecting (and
which is so far only part of containerd v1.1-rc). Luckily the version right
before standalone mode was deleted is available in a branch and supports the
required API version so switch to that here as a stop gap measure.
Note that the naming has changed kubernetes-incubator/cri-containerd →
containerd/cri-containerd → containerd/cri with the branch we are using being
at the middle step so update the naming and paths appropriately.
The command line options have changed a bit, so adjust.
Signed-off-by: Ian Campbell <ijc@docker.com>
|
|
This was referenced Apr 9, 2018
|
|
rn
approved these changes
Apr 9, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a carry of #68.
I needed to workaround
rootfsPropagation: sharedseemingly not working (maybe this is opencontainers/runc#1755, I need to investigate more to be sure).It was also necessary to bump a bunch of versions in the image cache and to update to a newer cri in lockstep (see the commit message for details).