On 05/04/2017 05:39 AM, [email protected] wrote: > > I can't find any justification for the api-server, controller-manager, > proxy and scheduler to be running and not pending (can't see anything > special in the user-data as well) >
The reason those pods are able to run despite the taints is that they're "static pods" created by the kubelet. The manifest is likely local on disk (e.g. in /etc/kubernetes/manifests), and the kubelet creates them and then reports a "mirror pod" to the api-server as a marker that the static pod is running. You can read more about them here: https://kubernetes.io/docs/concepts/cluster-administration/static-pod/ Best, Euan
signature.asc
Description: OpenPGP digital signature
