Update Kubernetes from v1.11.3 to v1.12.x #301
Merged
Conversation
This file contains 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
dghubble
changed the title
dghubble
force-pushed
the
update-kubernetes
branch
from
c955adb to
42ed257
Compare
dghubble
force-pushed
the
update-kubernetes
branch
from
42ed257 to
1690fa7
Compare
dghubble
force-pushed
the
update-kubernetes
branch
from
1690fa7 to
8f91208
Compare
|
I'm still on vacation and will get back to this. Most likely going to wait on a Kubernetes v1.12.1 to address the issues in v1.12.0. |
dghubble
force-pushed
the
update-kubernetes
branch
2 times, most recently
from
5e20f55 to
087cfd8
Compare
|
kubernetes/kubernetes#69062 fixed kubernetes/kubernetes#68986 and was cherry-picked into v1.12.1 in kubernetes/kubernetes#69117. I've checked that issue is solved on v1.12.1. |
dghubble
force-pushed
the
update-kubernetes
branch
3 times, most recently
from
7e42f83 to
d4e6256
Compare
|
The Kubernetes commit that broke the pod-checkpointer has been found, a change to the pod-checkpointer has been proposed and verified to solve the issue with recovery after power cycling. Once that merges and a new coreos/pod-checkpointer is published, v1.12 should be unblocked. |
dghubble
force-pushed
the
update-kubernetes
branch
2 times, most recently
from
00f0728 to
0dd9588
Compare
|
Typhoon v1.12.1 candidate passes conformance as-is and with kube-proxy in ipvs mode. |
This was referenced Oct 16, 2018
* Mount an empty dir for the controller-manager to work around kubernetes/kubernetes#68973 * Update coreos/pod-checkpointer to strip affinity from checkpointed pod manifests. Kubernetes v1.12.0-rc.1 introduced a default affinity that appears on checkpointed manifests; but it prevented scheduling and checkpointed pods should not have an affinity, they're run directly by the Kubelet on the local node * kubernetes-retired/bootkube#1001 * kubernetes/kubernetes#68173
dghubble
force-pushed
the
update-kubernetes
branch
from
0dd9588 to
9b6113a
Compare
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.
Trial the release candidates.
Known issues:
ClusterRole system:kube-controller-manager cannot get configmaps in v1.12.0-rc's kubernetes/kubernetes#68986(submitted a fix that's in v1.12.1 now)