Clean installation of cert-manager v1.14.4 on k3s v1.29.2+k3s1 gives error: resource mapping not found for ClusterIssuer

[sprijk]

Clean installation of cert-manager v1.14.4 on k3s v1.29.2+k3s1 gives error: resource mapping not found for ClusterIssuer

[sprijk]

Hi @hawksight,
I was following along this guide https://technotim.live/posts/kube-traefik-cert-manager-le/#cert-manager
The helm install worked successfully and took up to a 15 seconds to finish.

Not sure what could cause a delay (about 1 hour) before the ClusterIssuer resource was 'known'/accepted bij the k3s cluster.
It could be a k3s thing, although I dit not notice any other behavior with other CRDs.

The problem replicated is on my end (3 VMs on Proxmox).

I thought maybe this is a known issue.
However, if this problem is only on my end, I don't think we need to dig deeper.
But thanks for having looked into it!

[sprijk]

Weirdly enough, after 1 hour it works without the error mentioning the CRDs..?
What could cause this delay?

[hawksight]

Hey @sprijk - I was not able to reproduce this with k3d cluster locally, but I did notice it was slower to install than say kind which I normally use locally. This makes me think that perhaps the webhook component was perhaps not fully running after the install. Did the helm install finish correctly or time out after some time?

Perhaps you can share your cluster creation step?

Steps I used to try attempt to reproduce:

mkdir test-6879
cd test-6879
# Created the config files as you had them but with own email / domain in + switched to staging issuer for test purposes.
k3d cluster create test
k apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.4/cert-manager.crds.yaml
# Took a few seconds for this to complete
helm install cert-manager jetstack/cert-manager --namespace cert-manager --values=values.yaml --version v1.14.4 --create-namespace
# Took a minute or so to become ready - added `--create-namespace` for success too.
k apply -f secret-cf-token.yaml
k apply -f ci-letsencrypt-staging.yaml

[hawksight]

@sprijk thanks for the note. I suspect it probably is something about the environment too.
By closing this did you find the problem / solution or have you just moved onto another environment setup?