-
Notifications
You must be signed in to change notification settings - Fork 828
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
Donate Azure subscription to CNCF #1637
Comments
cc: @kubernetes/k8s-infra-team @caniszczyk FYI @kubernetes/release-engineering |
/cc |
/cc |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/remove-lifecycle stale |
/lifecycle frozen |
@caniszczyk @idvoretskyi - will this fit into the new program around cloud credits at CNCF? |
@dims can we kick-off the email thread please (with me and @caniszczyk)? |
Might be useful to bring me into the thread as well.
I’ve been working on both the Cloud Credits program and some earlier
conversations with Microsoft.
|
/priority important-longterm |
/assign @hh |
Looping in Lachie. /cc @lachie83 |
/close |
@ameukam: 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 have an Azure subscription dedicated to testing for various Kubernetes-related projects. It's been running well until we have to rotate this specific secret, which includes sharing with the test-infra on-call folks our credential (i.e. username, password, subscription ID, storage account key, etc all in plain text) used to authenticate test instances to create Kubernetes clusters on our Azure subscription. It's definitely not ideal and we would like to eliminate this process.
After having a conversation on Slack, it seems that the first step would be donating our Azure subscription/resources to the CNCF, which we would like to get some help with.
Our goals:
cluster
field in prow job config to reduce the chance of secrets being leakedHere is a list of projects that use the Azure subscription, and their core maintainers:
Thanks!
/cc @dims
The text was updated successfully, but these errors were encountered: