The problem in my case was because I had a broken kubeconfig(bad YAML) for kubelet, and later found kubelet ignores the kubeconfig flag if require-kubeconfig arg is not passed.
On Friday, 19 January 2018 10:18:11 UTC-6, jda...@redhat.com wrote: > > I had the same issue, which was caused by the fact that my > kube-controller-manager was misconfigured and therefore not running. > > I'd suggest checking logs for every daemon process and see "what else is > broken", in case that something else is the primary cause. > > Jan 19 17:01:04 nixos kube-controller-manager[18471]: F0119 > 17:01:04.695313 18471 node_controller.go:262] Controller: Invalid > clusterCIDR, mask size of clusterCIDR must be less than nodeCIDRMaskSize. > Jan 19 17:01:04 nixos systemd[1]: kube-controller-manager.service: Main > process exited, code=exited, status=255/n/a > Jan 19 17:01:04 nixos systemd[1]: kube-controller-manager.service: Unit > entered failed state. > Jan 19 17:01:04 nixos systemd[1]: kube-controller-manager.service: Failed > with result 'exit-code'. > > -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
