Skip to content
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

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

Closed
optix2000 opened this issue Jul 14, 2022 · 4 comments · Fixed by #1522
Labels

Comments

@optix2000
Copy link

optix2000 commented Jul 14, 2022

I'm getting the following error when trying to delete the addresspools or bgppeers CRDs.

% kubectl describe customresourcedefinitions.apiextensions.k8s.io addresspools.metallb.io
...
  Client Config:
        Ca Bundle:  Cg==
...
  Conditions:
    Last Transition Time:  2022-07-14T08:19:58Z
    Message:               no conflicts found
    Reason:                NoConflicts
    Status:                True
    Type:                  NamesAccepted
    Last Transition Time:  2022-07-14T08:19:58Z
    Message:               the initial names have been accepted
    Reason:                InitialNamesAccepted
    Status:                True
    Type:                  Established
    Last Transition Time:  2022-07-14T08:20:36Z
    Message:               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
    Reason:                InstanceDeletionFailed
    Status:                True
    Type:                  Terminating

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.

@fedepaol fedepaol added the bug label Jul 14, 2022
@fedepaol
Copy link
Member

So just to understand better the steps, you just installed and deleted the chart right?

@optix2000
Copy link
Author

In rapid succession, before any of the pods had started.

@fedepaol
Copy link
Member

Understood, thanks for the report

@optix2000
Copy link
Author

optix2000 commented Jul 14, 2022

Literally

helm repo add metallb https://metallb.github.io/metallb
helm install metallb metallb/metallb
# sleep 500
helm uninstall metallb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants