Open s1061123 opened 2 years ago
This will be taken care of myself, but to track it, open the issue.
I0126 05:53:57.786517 1 server.go:97] Neither kubeconfig file nor master URL was specified. Falling back to in-cluster config. I0126 05:53:57.971249 1 options.go:88] hostname: multus-service-controller-5685cb6f65-6kfjg I0126 05:53:57.971428 1 leaderelection.go:243] attempting to acquire leader lease kube-system/multus-service-controller... I0126 05:54:16.086651 1 leaderelection.go:253] successfully acquired lease kube-system/multus-service-controller I0126 05:54:16.086914 1 endpointslice_controller.go:259] Starting endpoint slice controller I0126 05:54:16.086932 1 shared_informer.go:240] Waiting for caches to sync for endpoint_slice I0126 05:54:16.086942 1 shared_informer.go:247] Caches are synced for endpoint_slice E0126 06:19:25.325444 1 leaderelection.go:325] error retrieving resource lock kube-system/multus-service-controller: Get "https://172.30.0.1:443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/multus-service-controller": context deadline exceeded I0126 06:19:25.325501 1 leaderelection.go:278] failed to renew lease kube-system/multus-service-controller: timed out waiting for the condition E0126 06:19:25.325560 1 leaderelection.go:301] Failed to release lock: resource name may not be empty F0126 06:19:25.325573 1 options.go:113] leaderelection lost
It might be come from testbed. So still in investigation.
This will be taken care of myself, but to track it, open the issue.