-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lots of "the server could not find the requested resource" errors #40
Comments
Thanks for the reply. I only set the groupName during helm installation, so anything else is default.
|
What version of webhook are you using? |
cert-manager-webhook-hetzner-1.2.2, installed via the helm chart. values.yaml only contains:
Multiple k3s clusters, all running v1.25.7+k3s1 |
Hi, kubectl api-resources Check which versions does your k8s API support. In my case, I'm running a kubeadm local 1.24 cluster and my highest supported version is: flowcontrol.apiserver.k8s.io/v1beta2 I'm still looking for the best way to fix this. EDIT: As stated here, flowcontrol.apiserver.k8s.io/v1beta3 should be supported from version 1.26 and later. |
Hi again, Upgrading to 1.26 fixes the issue. I deployed the cluster on Debian so I had to manually upgrade containerd to avoid kubelet to break. |
Is it not possible to use some old version compatible kubernetes 1.25.9? |
I found that cert-manager did not issue a certificate using webhook-hetzner today. The certificate stays in status "False". This did work last week, with the same version of the webhook.
Not sure if it is related, but I noticed that the webhook-hetzner pod spits out lots of warnings:
The text was updated successfully, but these errors were encountered: