Skip to content
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.

Sign up for GitHub

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

Jump to bottom

GCP support for Container OS #88

Closed
rsdcastro opened this issue Apr 17, 2018 · 2 comments
Closed

GCP support for Container OS #88

rsdcastro opened this issue Apr 17, 2018 · 2 comments

Comments

@rsdcastro
Copy link

From @rsdcastro on February 12, 2018 18:18

See #593 for reference.

Copied from original issue: kubernetes-retired/kube-deploy#595
@rsdcastro
Copy link
Author

Turning this into a GCP specific issue, as there's no current infrastructure or plans to have a more general Ubuntu support that works across providers.

cc @mkjelland @krousey @kcoronado

@rsdcastro rsdcastro mentioned this issue Apr 17, 2018
Closed
@rsdcastro rsdcastro added this to the cluster-api-beta-implementation milestone Apr 17, 2018
@roberthbailey roberthbailey mentioned this issue Jul 24, 2018
Closed
@roberthbailey
Copy link
Contributor

This issue was moved to kubernetes-sigs/cluster-api-provider-gcp#13

jayunit100 pushed a commit to jayunit100/cluster-api that referenced this issue Jan 31, 2020
@sidharthsurana @k8s-ci-robot
Fix the kubelet config for version 1.11 and above for worker nodes (k…
2e910e9 
…ubernetes-sigs#88)

The systemd unit definition of the kubelet sources the file
/etc/default/kubelet for any env variables. The default file
generated for /etc/default/kubelet has an empty value like
`KUBELET_EXTRA_ARGS=`. This causes the kubelet to not use the
actual value of KUBELET_EXTRA_ARGS set in the override file
/etc/systemd/system/kubelet.service.d/20-cloud.conf

This is the same fix as PR#68 which fixed this issue with master
node. This PR expands the same fix to worker nodes as well

The root issue is without this the kubelet on the node starts
without the `--cloud-provider=vsphere` flag causing the node to
be not recognized as a cloud instance

Change-Id: Ia73dc7e86ca193b42cea3ac7dc7cc22bebcd7ab4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rsdcastro @roberthbailey