-
Notifications
You must be signed in to change notification settings - Fork 97
Add assume role for Issuer #427
New issue
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
Add assume role for Issuer #427
Conversation
9b40996 to
ebfb00a
Compare
|
@nickperry Hi, thank you for moving this topic forward. I’ll test my PR this weekend! |
|
Just pushed a rebase to this PR. We will need to work on writing integration tests as well for this change since it's going to end up being a new support auth flow. |
6c1d47a to
9fe73ca
Compare
|
I’ve just renamed the attribute role -> roleArn. I have tested it locally, and everything looks good. If anyone would like to pick up and complete the tests, feel free to do so. |
|
I hate to do this, but can you change the role field back to just role? Cert-manager uses a role arn in one of its specs so we'd like to stay consistent with it: source: https://cert-manager.io/docs/configuration/acme/dns01/route53/#cross-account-access |
Not my PR so I can't push to it, but I have implemented the name change requested by @bmsiegel here if you want to cherry-pick it nickperry@a670b1c |
491b75a to
270e8e7
Compare
d2f851a to
901af13
Compare
|
We have been using this feature in non-prod at my organisation over the last few days and it works well. Thank you for implementing this @paragor. |
Signed-off-by: Egor Novikov <[email protected]> Signed-off-by: Brady Siegel <[email protected]>
901af13 to
24c3afc
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
48cbabb
into
cert-manager:main
Issue # 361
Closes # 361
Reason for this change
AWS RAM has restrictions that disallow issuing
isCA: truecerts from Subordinate AWS PCA.see https://docs.aws.amazon.com/privateca/latest/userguide/UsingTemplates.html
However, for example, Linkerd requires such a certificate.
This pull request allows for requesting an issue certificate directly from AWS PCA that is located in a different account.
Description of changes
A new optional field 'role' was added to Issuer and ClusterIssuer CRDs, which allows assuming a role for another account and working with AWS PCA from a different account.