Approve the signing requests with kubectl certificates approve ....
Delete the namespace TEST
Repeat 1-4
The second time around however, the cluster wide approvals still exist but the secrets that stored the certificates in the namespace TEST are gone. So request-cert attempts new requests. This however causes the request-cert to fail "already exists" error. I think I've found the culprit and I'm wondering why the initial request isn't allowed to use previous requests.
This is my scenario:
kubectl certificates approve ...
.The second time around however, the cluster wide approvals still exist but the secrets that stored the certificates in the namespace TEST are gone. So request-cert attempts new requests. This however causes the request-cert to fail "already exists" error. I think I've found the culprit and I'm wondering why the initial request isn't allowed to use previous requests.