mirrors/external-dns
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/external-dns.git synced 2025-08-07 01:56:57 +02:00
Code Issues Packages Projects Releases Wiki Activity

Document usage of AWS env vars

Browse Source 
Document the working method of using environment variables on the external-dns deployment to avoid the overhead of kiam or kube2iam when not using EKS
This commit is contained in:
nadilas 2021-09-01 22:53:13 +02:00 committed by GitHub
parent bf3a91f7f7
commit 07115e4092
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/tutorials/aws.md
View File

@ -55,7 +55,7 @@ If your EKS-managed cluster is >= 1.13 and was created after 2019-09-04, refer
to the [Amazon EKS to the [Amazon EKS
documentation](https://docs.aws.amazon.com/eks/latest/userguide/create-service-account-iam-policy-and-role.html) documentation](https://docs.aws.amazon.com/eks/latest/userguide/create-service-account-iam-policy-and-role.html)
for instructions on how to create the IAM Role. Otherwise, you will need to use for instructions on how to create the IAM Role. Otherwise, you will need to use
kiam or kube2iam. kiam or kube2iam or set the environment variables AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY on the deployment.
### kiam ### kiam