Ilsa Loving

Hot damn! That's a fantastic improvement over what was before. I'll try to go through it when I have a chance. Thank you SO much for all your work!

That's because you loaded a management one. Load one that _isn't_ management.

Exactly. It _could_ be fixed, by changing the json name to `traffictype` maybe, but that entirely depends on what the underlying library sends you. If it sends you incorrect data,...

What do you need me to do? The output from the PR looks good, I guess?

Since I don't have an ingress yet, I tried adding the revisionhistorylimit annotation to the clusterissuer but that didn't do anything.

I tried using 1.18.3 instead but I'm still having the same problem. According to [this](https://cert-manager.io/docs/tutorials/certificate-defaults/, as of 1.18 the default is _supposed_ to be 1. Apparently somebody forgot to actually...

Issuer Config [pki_issuer.yaml](https://github.com/user-attachments/files/23398467/pki_issuer.yaml) Here is the cert that I made: [pki_cert.yaml](https://github.com/user-attachments/files/23398457/pki_cert.yaml) Cert describe [certstatus.yaml](https://github.com/user-attachments/files/23398560/certstatus.yaml) CR describe [cr_status.yaml](https://github.com/user-attachments/files/23398574/cr_status.yaml)

Seems like there are a couple things going on. It continuously spews CRs without giving vault a chance to respond to the previous one. Also, I see this event: "Issuing...

Switching to sign fixed the problem. Is there some way to short circuit the process so that certmanager doesn't go insane if there's a config issue? I might have figured...

I just opened a ticket for what may be the same problem, and I've tried both 1.18.3 and 1.19.1. When I create a cert resource, certmanager start spewing CR revisions...