Deleting CRD results in could not list instances: unable to find a custom resource client for addresspools.metallb.io: unable to load root certificates: unable to parse bytes as PEM block
#1501
Labels
I'm getting the following error when trying to delete the
addresspools
orbgppeers
CRDs.Installed MetalLB using the metallb Helm chart
v0.13.3
from https://metallb.github.io/metallb.I then deleted the helm install shortly after when I realized it was installed to the wrong namespace.
Running k3s:
v1.23.8+k3s2
Using Cilium
v1.11.6
Presumably, this is because I deleted the controller before the CA could be populated here. Assuming that's the case, it's probably worth putting a "real" dummy CA so the CRD can be deleted if the controller never started.
Seeking some advice on whether it's safe to force delete the CRD and to see if adding a CA is a valid solution.
The text was updated successfully, but these errors were encountered: