-
Notifications
You must be signed in to change notification settings - Fork 791
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
[Umbrella Issue] AWS Infrastructure for Kubernetes #4654
Comments
/milestone v1.27 |
@ameukam: The label(s) 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. |
To start:
|
cc @sftim |
Support of the management account is upgraded to the |
Hey @ameukam, I would like to contribute in this. Regards. |
@devarsh10 Feel to look at the issues with the label We mainly use Terraform for the moment to manage our AWS resources. |
Okay. Regards. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/close it's been a year! we have set up a whole bunch of things :) |
@dims: Closing this issue. 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. |
We got 3M of AWS credits for 2023.
We need to setup a new infrastructure that gonna be use for
The text was updated successfully, but these errors were encountered: