-
Notifications
You must be signed in to change notification settings - Fork 41.5k
Move Vagrant provider to Flannel #13986
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
Move Vagrant provider to Flannel #13986
Conversation
As for why I cannot use the kubelet provisioned etcd to hold flannel configuration, its a chicken/egg problem since I need to configure flannel before I install/run docker and/or kubelet. |
Fyi #13877 |
@bprashanth - I would like this to go in before #13877 because it's easier to backport to 1.0.x stream, works, and unblocks folks. I hope this change will make it easier to then have vagrant included in the changes for #13877 |
Labelling this PR as size/L |
GCE e2e build/test passed for commit 360e762. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be in an else block? For the platforms that don't have a host etcd, we don't need this rule to execute.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No.
Even though we run the default kubernetes etcd via a pod, we bind mount that directory in for logging, so we need to touch the files first in order to allow the mount to proceed.
See https://github.com/kubernetes/kubernetes/blob/master/cluster/saltbase/salt/etcd/etcd.manifest#L41
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it, thanks.
@derekwaynecarr I can confirm this pr fixes #11119 for me, everything works fine, except that there is a failed unit(
|
@tsl0922 - the docker storage setup unit failure is fine, and results in using devicemapper. I will move to overlayfs when its stable. Thanks for testing the feature! |
LGTM. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit 360e762. |
Automatic merge from SubmitQueue |
Auto commit by PR queue bot
…f-#13986-upstream-release-1.0 Automated cherry pick of #13986
Works for me, although still have issues accessing https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/kube-dns, but think it is related to something else. |
This PR makes the following changes:
Fixes #13920
Fixes #11119
Once this lands, I will back port it to 1.0.x release stream.