[aws] Need a new AWS account to replace 607362164682

[dims]

Folks,

I've been wondering about account 607362164682 and finally tracked it down. Once upon a time @gyuho created this account for some of the AWS
related repositories that needed to run CI jobs.

Let's please create a new account from our AWS credits to replace this account.

References:

• https://cs.k8s.io/?q=607362164682&i=nope&files=&excludeFiles=audit&repos=
• kubetest: add EKS plugin test-infra#9811
• https://github.com/kubernetes/test-infra/pull/10868/files#diff-b6b7a809f492819b6087cd9c020844bcc1671c578abaa25f18cec5ff79c6ca28R3

Query to find instances to fix:

• https://cs.k8s.io/?q=preset-aws-credential-aws-(oss%7Cshared)&i=nope&files=&excludeFiles=&repos=

Repositories

• aws-ebs-csi-driver ( Switch to new s3 bucket in AWS community account kubernetes-sigs/aws-ebs-csi-driver#1745 needs to merge )
• aws-efs-csi-driver ( Move to new s3 bucket kubernetes-sigs/aws-efs-csi-driver#1137 needs to merge )
• aws-fsx-csi-driver ( Move to new s3 bucket kubernetes-sigs/aws-fsx-csi-driver#354 needs to merge )
• aws-fsx-openzfs-csi-driver
• aws-iam-authenticator
• aws-load-balancer-controller
• cloud-provider-aws
• secrets-store-csi-driver

[dims]

@xmudrii @ameukam - how about k8s_infra_eks_e2e_shared_001 as the name

Since:

• We used k8s_infra_eks_e2e_boskos_XXX pattern in Add boskos accounts for EKS build cluster #5185
• But this is not boskos
• And this goes into a shared credential file ( https://github.com/kubernetes/test-infra/blob/e4624a5858a436fb4d238e7580fa712537255c6f/config/jobs/kubernetes/sig-cloud-provider/aws/sig-aws-credentials.yaml#L18-L30 )

[BenTheElder]

lol @dims from https://github.com/kubernetes/test-infra/pull/10868/files#diff-b6b7a809f492819b6087cd9c020844bcc1671c578abaa25f18cec5ff79c6ca28R3

see my old comment:
https://github.com/kubernetes/test-infra/pull/10868/files#r249988768

looks like currently this is primarily used to test AWS integrations, can we pivot to using a boskos pool for these jobs?
https://github.com/search?q=repo%3Akubernetes%2Ftest-infra%20preset-aws-credential-aws-oss-testing&type=code

[BenTheElder]

Or else if not shared boskos, this should probably be N different accounts? so we can better track billing, since it's being used for different subprojects (storage, loadbalancer, etc).

[ameukam]

LGTM for the naming pattern.

+1 on moving to a boskos pool.

[xmudrii]

+1 for the naming pattern and moving to a boskos pool if possible.

[dims]

+1 to boskos as follow ups (we can do it repo by repo with a follow up umbrella issue)

@nnmin-aws had offered to help

[nckturner]

Once we have the account we will need to determine what resources are missing in order to run the CI jobs (there may be IAM roles, S3 buckets, etc) and we also need a new injectable secret like we have now that prow jobs can add to their spec. I'd be interested to know how that was set up actually, i.e. is it creds for an IAM user? I suppose only @shyamjvs knows :)

[dims]

@xmudrii @ameukam @BenTheElder ... so the note from @nckturner precludes us to switch to boskos immediately.

Let's create this account k8s_infra_eks_e2e_shared_001 and get some experience with moving jobs one by one and during the process identify stuff we will need to automate to eventually switch to boskos accounts ... (E_DONT_KNOW_IF_WE_WILL_GET_THERE!)

[torredil]

We use 607362164682 over at kubernetes-sigs/aws-ebs-csi-driver.

Just a few things we need to take care of here, we'll need to create an S3 bucket k8s-kops-csi-e2e with write access in the new account and access to an ECR repository aws-ebs-csi-driver in us-west-2 to push the images built for testing.

Lets ensure https://github.com/kubernetes-sigs/boskos/tree/master/aws-janitor runs against the new account to cleanup any leaked resources.

[ameukam]

@dims @xmudrii can we close this ? is there any follow-up to do ?

[xmudrii]

@ameukam I'm not really sure what's the status of this, @dims might know better

[dims]

we still need this. let's create a new one k8s_infra_eks_e2e_shared_001 and replace usage of 607362164682 over time slowly

[dims]

new account is 209411653980

[dims]

calling it! done!

[dims]

thanks to everyone who helped with fixing things, reviews and approvals

/close

[k8s-ci-robot]

@dims: Closing this issue.

In response to this:

thanks to everyone who helped with fixing things, reviews and approvals

/close

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.

[ameukam]

/sig k8s-infra
/kind cleanup
/milestone v1.29
/area infra/aws