-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Make AWS credentials configurable easily #10868
Make AWS credentials configurable easily #10868
Conversation
Ok this is more readable 👍 /lgtm |
LGTM label has been added. Git tree hash: 543fbdf5bec90392425c253c18c3ed61636e29ec
|
@@ -10,7 +10,7 @@ presubmits: | |||
context: pull-security-kubernetes-e2e-aws-eks-1-11-correctness | |||
labels: | |||
preset-kubernetes-e2e-aws-eks-1-11: "true" | |||
preset-kubernetes-e2e-aws-eks-common: "true" | |||
preset-aws-credential: "607362164682" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Btw - the label value is our testing account's ID. We can add new presets with different accounts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect this will be error prone as nearly all of us (including me) don't have access to and have no idea what these are so we'll just be copying around mysterious number strings. I'd strongly suggest giving these a human readable name and commenting with the ID# on the preset instead.
Doing that would also mean you can swap accounts without mass updating all of the job config files, which is a big reason presets are useful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something like:
preset-aws-credential: cncf-prow
preset-aws-credential: aws-eks
Which will also be useful because eventually @kubernetes/k8s-infra-wg will probably want to track usage on the CNCF credentials.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Naming them with intent should also help job writers to figure out which they should be using from example jobs. The opaque strings will probably lead to someone creating a charts job on the wrong account or something.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@BenTheElder Sounds reasonable.. Will change it to something more meaningful, thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done, PTAL.
f866af5
to
60a9ee0
Compare
Presubmit failed due to /cc @BenTheElder |
e0b6b36
to
dafe48e
Compare
labels: | ||
preset-kubernetes-e2e-aws-eks-common: "true" | ||
preset-aws-credential: "aws-oss-testing" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we put a comment describing what the usage should be?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. Added comment above preset definition.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, this should be a nice step towards being easier to follow the config :-)
dafe48e
to
9d607b5
Compare
- name: AWS_K8S_TESTER_EKS_AWS_IAM_AUTHENTICATOR_DOWNLOAD_URL | ||
value: https://amazon-eks.s3-us-west-2.amazonaws.com/1.11.5/2018-12-06/bin/linux/amd64/aws-iam-authenticator | ||
# AWS test account credential mounted path, required for AWS API call | ||
# Credentials for using AWS test account 607362164682. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will leave for a follow-up, but perhaps the intention of who should be using this account for what kind of testing? :^)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm soon planning to organize all aws testing account creds at a central place under jobs/sig-aws/
. Working with @krzyzacy to get the prow secrets right. I'll clarify it in follow-up PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #10886
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder, gyuho, shyamjvs 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 |
LGTM label has been added. Git tree hash: 650d8d00cb430b39462c8e900d9a8e862aff351a
|
@shyamjvs: Updated the
In response to this:
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. |
Follow-up of #10866
This change standardizes way we pass credentials to kops/eks jobs - allowing to do testing in newer accounts.
/cc @gyuho