-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Fix Vagrant kube-up - missed file watch on systemd stops kubelet starting on initial kube-up #10492
Fix Vagrant kube-up - missed file watch on systemd stops kubelet starting on initial kube-up #10492
Conversation
GCE e2e build/test failed for commit 5122ea42f45e04d1e0573f8fc3fcd8f3d6230de4. |
LGTM; I'll have a merge conflict but no big deal. As I commented on #10488, I worry that we have deeper issues with Salt & systemd (saltstack/salt#16778), but we should express our dependencies (as in this PR) even if Salt isn't doing the right thing. |
5122ea4
to
de78898
Compare
@zmerlynn - can you look at this today? it is blocking basic creation of kube cluster. |
@derekwaynecarr: Absolutely, when I saw that I screwed up it not making 0.20.2, I hung my head in shame. But we may actually have a 0.20.3. |
LGTM |
@dchen1107 for rubber stamp |
GCE e2e build/test passed for commit de78898. |
Cherrypick for 0.20. #10409 |
LGTM. Thanks for fixing it. |
@thockin second TL approval, please? |
LGTM |
Fix Vagrant kube-up - missed file watch on systemd stops kubelet starting on initial kube-up
The Kubelet was not starting because service.running phase of Kubelet was executing before the service file was authored to disk when on systemd environment.
Fixes #10522