Divyansh Gupta
Divyansh Gupta
Hi @kcraley, thanks for bringing this to our attention. This is definitely something that we will fix, but will likely not be treated as a high priority bug and may...
Hi @ceastman-r7 . We have placed this change in our priority queue, thank you for the suggestion.
Hi @bashiru98 - this Github repository focuses on this Plugin. Questions about getting certificates to work with NLB are best directed at AWS support. AWS does have two guides up...
@ibrahimjelliti Right now, there is no workaround to this. This plugin currently only supports and tests with AL2.
``` Observed Generation: 1 Reason: Failed Status: False Type: Issuing Last Transition Time: 2023-10-10T13:37:18Z Message: Issuing certificate as Secret does not exist Observed Generation: 1 Reason: DoesNotExist Status: False Type:...
I was able to reproduce and cut this SIM to cert-manager: https://github.com/cert-manager/cert-manager/issues/6405. I saw that one of the times I reproduced, if I waited long enough, it did retry exactly...
I was able to get retries to work, see https://github.com/cert-manager/cert-manager/issues/6405 for details. It seems the retries just take longer between each try than they did before, which was a change...
Hi @woehrl01 - let me share with your my results when replicating the exact situation you described: 1. Create the certificate with NO issuer in place and describe it: ```...
There seem to be two distinct problems: 1. Upon a successful retry after an initial failure, it seems that Certificate objects are not always being marked as successfully issued the...
Hi @woehrl01 - thank you! Noting the bot here: ``` Detected different CRDs in the config/crd/bases directory and charts/aws-pca-issuer/crds directory. Since both CRDs were modified in this commit(s), they were...