Attempting to update Cert-Manager through TrueNAS via TrueCharts repository about cert-manager

[voltane]

I found a solution by the way :D It was announced on TrueCharts Discrod 7.11.2023.

Cert-Manager update issues

Users having problems with updating cert-manager from the operators train will have to run:
k3s kubectl delete --grace-period 30 --v=4 -k https://github.com/truecharts/manifests/delete4
Then try the update again
Do an edit of cluster-issuer without any changes and save...

In edgecases where this does not work correctly, please follow the instructions below at your own risk
Find out if there are any crd objects left by running k3s kubectl get crd -A | grep "cert-manager"

Run the following, replacing "REPLACE" with the name of the object identified with the command above:
k3s kubectl delete crd REPLACE (Note, if stuck for a minute or two, just hit ctrl+c and continue)
k3s kubectl patch crd/REPLACE -p '{"metadata":{"finalizers":[]}}' --type=merge

For me after first suggested command to run, cert-manager updated correctly to latest version. Cheers!

[BeatSpark]

Darn. Now's a bad time to mention that I just filed the ticket.

Though it's still something that'd be handy for them to fix.

truecharts/charts#16561

[voltane]

I'm pretty sure that this error has nothing to do with cert-manager itself. Its rather related with cert-manager definition created by TrueCharts for TrueNAS environment. Better file a ticket here: https://github.com/truecharts/charts/issues.
Anyways, i'm also getting the same error and still looking for solution ;)

[BeatSpark]

Cheers. I'll go and close this and refile a fresh ticket over there.

I'll add in a link for you to the new one before I close this tho.

[BeatSpark]

Just for my own reference, since I really don't know how to do much when it comes to the non-gui side, minus your general navigation of a Linux file system, how would I go about doing this fix?

[voltane]

On Your TrueNAS Scale go to System Settings > Shell. There You can run commands mentioned above.

[BeatSpark]

I had tried that initially, given it's a copy-paste solution, although it threw up this error:
WARN[0000] Unable to read /etc/rancher/k3s/k3s.yaml, please start server with --write-kubeconfig-mode to modify kube config permissions error: error loading config file "/etc/rancher/k3s/k3s.yaml": open /etc/rancher/k3s/k3s.yaml: permission denied

Unless I need to login as root-

[voltane]

Indeed You have to login as root.

[BeatSpark]

Yep, cool, got that sorted.

Glad to see that the 'Updates available' tag is gone now. Holy crap.

[voltane]

Good to hear that. Besides that i'm not a discord-guy and i'm not using it on my daily basis, i encourge You to join their Discord here https://truecharts.org/s/discord. A lot of issues has a solution there which are not available elsewhere.