Failed to start Kubernetes API Server after reboot #70
Description
Describe the bug
After restarting the holorouter, webtop became unavailable. When trying to run some kubectl commands, such as kubectl get pods, I noticed some API errors were displayed.
After checking systemctl status kube-apiserver, the message was:
Failed to start Kubernetes API Server
After checking journalctl -u kube-apiserver.service -b the message was:
Nov 07 00:07:35 holorouter systemd[1]: Starting Kubernetes API Server...
Nov 07 00:07:35 holorouter kube-apiserver[1512]: W1107 00:07:35.065852 1512 services.go:37] No CIDR for service cluster IPs specified. Default value which was 10.0.0.0/24 is deprecated and will be removed in future releases. Please specify it using --service-cluster-ip-range >
Nov 07 00:07:35 holorouter kube-apiserver[1512]: I1107 00:07:35.065933 1512 server.go:554] external host was not specified, using 10.0.33.99
Nov 07 00:07:35 holorouter kube-apiserver[1512]: W1107 00:07:35.065966 1512 authentication.go:525] AnonymousAuth is not allowed with the AlwaysAllow authorizer. Resetting AnonymousAuth to false. You should use a different authorizer
Nov 07 00:07:35 holorouter kube-apiserver[1512]: E1107 00:07:35.066391 1512 run.go:74] "command failed" err="[--etcd-servers must be specified, service-account-issuer is a required flag, --service-account-signing-key-file and --service-account-issuer are required flags]"
Nov 07 00:07:35 holorouter systemd[1]: kube-apiserver.service: Main process exited, code=exited, status=1/FAILURE
Nov 07 00:07:35 holorouter systemd[1]: kube-apiserver.service: Failed with result 'exit-code'.
Nov 07 00:07:35 holorouter systemd[1]: Failed to start Kubernetes API Server.
Any tips on how to reconfigure the holorouter without resetting it? I already have an Instance deployed.
Reproduction steps
...
Expected behavior
I need to reconfigure holorouter webtop without reseting it.
Additional context
No response