You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cannot start. but it works well in lower version k3s, same config.
I1001 14:27:35.491252 1 secure_serving.go:116] Serving securely on [::]:443
E1001 14:27:35.517467 1 webhook.go:196] Failed to make webhook authorizer request: the server could not find the requested resource
E1001 14:27:35.517767 1 errors.go:77] the server could not find the requested resource
E1001 14:27:36.145336 1 webhook.go:196] Failed to make webhook authorizer request: the server could not find the requested resource
E1001 14:27:36.145415 1 errors.go:77] the server could not find the requested resource
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 26m default-scheduler Successfully assigned cert-manager/alidns-webhook-9b94b9494-bf74d to tower
Normal Pulled 25m (x2 over 26m) kubelet Container image "pragkent/alidns-webhook:0.1.0" already present on machine
Normal Created 25m (x2 over 26m) kubelet Created container alidns-webhook
Normal Started 25m (x2 over 26m) kubelet Started container alidns-webhook
Warning Unhealthy 25m (x6 over 26m) kubelet Liveness probe failed: HTTP probe failed with statuscode: 500
Normal Killing 25m (x2 over 25m) kubelet Container alidns-webhook failed liveness probe, will be restarted
Warning BackOff 6m27s (x72 over 23m) kubelet Back-off restarting failed container
Warning Unhealthy 79s (x75 over 26m) kubelet Readiness probe failed: HTTP probe failed with statuscode: 500
The text was updated successfully, but these errors were encountered:
cannot start. but it works well in lower version k3s, same config.
The text was updated successfully, but these errors were encountered: