https://bugzilla.redhat.com/show_bug.cgi?id=1315472

hong 511173846@qq.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |511173846@qq.com

--- Comment #5 from hong 511173846@qq.com --- ult config: unable to load in-cluster configuration, KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT must be defined Dec 11 10:35:19 master01 kube-controller-manager: invalid configuration: no configuration has been provided Dec 11 10:35:19 master01 systemd: kube-controller-manager.service: main process exited, code=exited, status=1/FAILURE Dec 11 10:35:19 master01 systemd: Unit kube-controller-manager.service entered failed state. Dec 11 10:35:19 master01 systemd: kube-controller-manager.service failed. Dec 11 10:35:19 master01 systemd: kube-controller-manager.service holdoff time over, scheduling restart. Dec 11 10:35:19 master01 systemd: --experimental-cluster-signing-duration=87600h0m0s': /opt/k8s/conf/kube-controller-manager.env Dec 11 10:35:19 master01 kube-controller-manager: I1211 10:35:19.911712 124830 serving.go:319] Generated self-signed cert in-memory Dec 11 10:35:19 master01 kube-controller-manager: W1211 10:35:19.911767 124830 client_config.go:541] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work. Dec 11 10:35:19 master01 kube-controller-manager: W1211 10:35:19.911774 124830 client_config.go:546] error creating inClusterConfig, falling back to default config: unable to load in-cluster configuration, KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT must be defined Dec 11 10:35:19 master01 kube-controller-manager: invalid configuration: no configuration has been provided Dec 11 10:35:19 master01 systemd: kube-controller-manager.service: main process exited, code=exited, status=1/FAILURE Dec 11 10:35:19 master01 systemd: Unit kube-controller-manager.service entered failed state. Dec 11 10:35:19 master01 systemd: kube-controller-manager.service failed. Dec 11 10:35:20 master01 systemd: kube-controller-manager.service holdoff time over, scheduling restart. Dec 11 10:35:20 master01 systemd: --experimental-cluster-signing-duration=87600h0m0s': /opt/k8s/conf/kube-controller-manager.env Dec 11 10:35:20 master01 kube-controller-manager: I1211 10:35:20.527572 124838 serving.go:319] Generated self-signed cert in-memory Dec 11 10:35:20 master01 kube-controller-manager: W1211 10:35:20.527650 124838 client_config.go:541] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work. Dec 11 10:35:20 master01 kube-controller-manager: W1211 10:35:20.527660 124838 client_config.go:546] error creating inClusterConfig, falling back to default config: unable to load in-cluster configuration, KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT must be defined Dec 11 10:35:20 master01 kube-controller-manager: invalid configuration: no configuration has been provided Dec 11 10:35:20 master01 systemd: kube-controller-manager.service: main process exited, code=exited, status=1/FAILURE Dec 11 10:35:20 master01 systemd: Unit kube-controller-manager.service entered failed state. Dec 11 10:35:20 master01 systemd: kube-controller-manager.service failed. Dec 11 10:35:20 master01 systemd: kube-controller-manager.service holdoff time over, scheduling restart. Dec 11 10:35:20 master01 systemd: start request repeated too quickly for kube-controller-manager.service Dec 11 10:35:20 master01 systemd: Unit kube-controller-manager.service entered failed state. Dec 11 10:35:20 master01 systemd: kube-controller-manager.service failed. [root@master01 ansible]# cat /etc/redhat-release CentOS Linux release 7.6.1810 (Core) [root@master01 ansible]#

hi, when i install the kubernetes via binary,i got the same bug.

the install version is kubernetes-server-linux-amd64-1.16.tar.gz and my system environment is CentOS Linux release 7.6.1810 (Core).