We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://docs.kuadrant.io/0.11.0/kuadrant-operator/doc/user-guides/secure-protect-connect-single-multi-cluster/#step-3-add-a-tls-issuer
Before creating ClusterIssuer, aws-credentials Secret must be created in cert-manager namespace.
aws-credentials
cert-manager
kubectl -n cert-manager create secret generic aws-credentials \ --type=kuadrant.io/aws \ --from-literal=AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID \ --from-literal=AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY
This requirement is documented here: https://cert-manager.io/docs/configuration/acme/dns01/route53/#iam-user-with-long-term-access-key
The text was updated successfully, but these errors were encountered:
This will be fixed by this PR which should shortly land for 1.0.x:
fixed in the 1.0.x guides.
Sorry, something went wrong.
No branches or pull requests
https://docs.kuadrant.io/0.11.0/kuadrant-operator/doc/user-guides/secure-protect-connect-single-multi-cluster/#step-3-add-a-tls-issuer
Before creating ClusterIssuer,
aws-credentials
Secret must be created incert-manager
namespace.This requirement is documented here: https://cert-manager.io/docs/configuration/acme/dns01/route53/#iam-user-with-long-term-access-key
The text was updated successfully, but these errors were encountered: