-
Notifications
You must be signed in to change notification settings - Fork 16.7k
[stable/external-dns] Addded a parameter for supporting --aws-assume-… #12164
Conversation
…role flag in external-dns Signed-off-by: Enis Soztutar <enis@cloudera.com>
Hi @enis. Thanks for your PR. I'm waiting for a helm member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign @viglesiasce |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
/assign @prydonius |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
/ok-to-test |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: davidkarlsen, enis 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 |
…role flag in external-dns (helm#12164) Signed-off-by: Enis Soztutar <enis@cloudera.com>
…role flag in external-dns
Signed-off-by: Enis Soztutar enis@cloudera.com
What this PR does / why we need it:
external-dns supports a command line flag
--aws-assume-role
implemented via kubernetes-sigs/external-dns#524, but the helm chart does not support this. This jira adds supports for the command line option.Special notes for your reviewer:
There is also a related roleArn parameter, but that works a bit differently since it sets the role to assume using aws default credentials. roleArn requires setting secret and access keys. Sending the
--aws-assume-role
is different since it will work with instance profile creds.@jvassev may want to take a look.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]