Previously when setting the external cloud controller manager
configuration the core components `kubelet`, `apiserver` and
`kubecontroller-manager` were configured to use the external cloud
controller manager. Without setting the feature flag
EnableExternalCloudController this lead to a cluster in which the
masters had the cloud controller taint
`node.cloudprovider.kubernetes.io/uninitialized` which prevents
essential pods, like dns-controller to not be scheduled and leaves a
cluster where worker nodes can't connect to the api server because they
cannot resolve its hostname.
We don't call klog.InitFlags yet, because that will cause a flag
redefinition error until we get everyone to stop using glog. That
will happen when we update to k8s 1.13.
This currently just turns off validation of the kubelet cluster dns
flag, which should allow for experimenting with more complicated DNS
configurations such as local proxies, which may address shortcomings
of DNS retries with UDP.
Issue #5584
Automatic merge from submit-queue.
Let a user set a hostnameOverride when the cloud provider is aws.
Let a user use the hostname or set a hostnameOverride when the cloud provider is aws. This would allow for a more descriptive name to be used. The name of the hosts when using @hostname can be set by using a hook or some other method.
User reports of kubelet flags not being passed; moved more to code.
Also found & fixed the likely root-cause issue: we have two copies of
the cluster spec and were not being precise about which one we wanted to
use at all times.
Otherwise we were not evicting based on low inodes
Also add the notion of a flag-default, so we can pass fewer spurious
flags, and gget closer to the component model
Xiaoyu Zhong
Michael Wagner
tanjunchen
mikesplain
Peter Rifel
Justin SB
Lily
Michael Taufen
Justin Santa Barbara
Rohith
andrewsykim
Tim Hockin
zhangxiaoyu-zidif
Kubernetes Submit Queue
zengchen1024
Rodrigo Menezes
wlan0
Andrey Chernih
andrewsykim
Chris Love
Abrar Shivani
SandeepPissay