Skip to content
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

Create AWS Access for Kubermatic to create prow clusters #4748

Closed
hh opened this issue Feb 9, 2023 · 6 comments
Closed

Create AWS Access for Kubermatic to create prow clusters #4748

hh opened this issue Feb 9, 2023 · 6 comments
Assignees
Labels
area/infra/aws Issues or PRs related to Kubernetes AWS infrastructure priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.
Milestone

Comments

@hh
Copy link
Member

hh commented Feb 9, 2023

@xmudrii and the team at Kubermatic need AWS creds.

Would be good to document the process for either the AWS Account or IAM user creation process here:
https://github.com/kubernetes/k8s.io/blob/main/infra/aws/terraform/README.md#infraawsterraform

This is in support of #4686

@hh hh added the sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. label Feb 9, 2023
@ameukam
Copy link
Member

ameukam commented Feb 9, 2023

/assign @jeefy

/area infra/aws
/priority important-soon
/milestone v1.27

@k8s-ci-robot k8s-ci-robot added the area/infra/aws Issues or PRs related to Kubernetes AWS infrastructure label Feb 9, 2023
@k8s-ci-robot k8s-ci-robot added this to the v1.27 milestone Feb 9, 2023
@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Feb 9, 2023
@hh
Copy link
Member Author

hh commented Feb 9, 2023

@ameukam I can create this manually now, or you can document approach you want.

@ameukam
Copy link
Member

ameukam commented Feb 9, 2023

@ameukam I can create this manually now, or you can document approach you want.

I'll defer to @jeefy on the approach here. Possible he need one sync with Kubermatic folx before we do something.

@jeefy
Copy link
Member

jeefy commented Feb 9, 2023

I think our default state for the next ~1.5mo is "move (reasonably) fast and do true best practices later" so yeah, I say @hh unblock @xmudrii and create them manually.

P-1 and P0 aren't "do the best thing first", and doing this sooner gives us breathing room to do it right later.

@hh
Copy link
Member Author

hh commented Feb 9, 2023

I've created [email protected] and given the password to Kubermatic

@hh hh closed this as completed Feb 10, 2023
@ameukam
Copy link
Member

ameukam commented Feb 12, 2023

xRef: #4686

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/infra/aws Issues or PRs related to Kubernetes AWS infrastructure priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.
Projects
Status: Done
Development

No branches or pull requests

4 participants