-
Notifications
You must be signed in to change notification settings - Fork 835
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
Setup autobump job for k8s-infra prow clusters #1742
Comments
/milestone v1.22 |
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 |
/milestone v1.23 |
/assign Work to get this done:
Things that could be done as followup:
|
PR to add the job to kubernetes/test-infra: kubernetes/test-infra#23048 |
#2407 - there's a real live autobump, so this job works |
/close |
@spiffxp: 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. |
#1740 was a trial run of using
autobumper
from kubernetes/test-infra to automatically bump:Let's setup a user for this, get their secrets in the trusted build cluster, and setup a periodic job to use this config.
A followup from this would be to do the same for apps deployed to
aaa
, but they need to be auto-deployed first./sig testing
/area prow
/area cluster-mgmt
/priority important-soon
/milestone v1.21
The text was updated successfully, but these errors were encountered: