[Feature Request]: Integration with cert-manager 1.10 about aws-privateca-issuer HOT 4 CLOSED

Thank you for raising this issue with the AWS Private CA Issuer plugin. We will review your submission and respond back to you here as soon as possible.

from aws-privateca-issuer.

Hi @scottd018, can you check your aws-privateca-issuer logs? When I run the e2e tests (successfully), I get the same log as you but then

Found status change for Certificate "1669167833--ec-issuer-secret-sub-ca-certificate" condition "Ready": "False" -> "True"; setting lastTransitionTime to 2022-11-23 01:44:55.839946709 +0000 UTC m=+8455.518930157

Just after it. A successful issuance looks like this in the privateca-issuer logs

{"level":"info","ts":1669167892.6135132,"logger":"controllers.CertificateRequest","msg":"Created certificate with arn: arn:aws:acm-pca:us-east-1:718389859439:certificate-authority/5e91c803-bd7f-4a7b-961a-bd4589e88758/certificate/830472b4743b648356b6f7d2c982f56d","certificaterequest":"pca-issuer-ns-1669167833/1669167833--ec-issuer-secret-sub-ca-certificate-4xmbj"}

You can find your issuer pod by running kubectl get pods -A

from aws-privateca-issuer.

Hey @bmsiegel , sorry it took so long to get back to this. I see you've opened an issue for this in the cert-manager repo. Is it fair to say that, based on what I see in the other issue, that this is a benign issue and can be safely ignored? Just want to confirm. Thanks!

from aws-privateca-issuer.

Hi @scottd018,

No worries. This is correct, from my side I'm still seeing successful issuance.

Thanks for bringing the issue up. I'm going to close for now but if you see issues please let us know!

from aws-privateca-issuer.