-
Notifications
You must be signed in to change notification settings - Fork 854
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
Migrate slack-infra to community built/hosted images #905
Comments
/assign @bartsmykla @ameukam |
I was waiting kubernetes-sigs/slack-infra#31 to get merge. I'll make another PR. |
Context: kubernetes/k8s.io#905 (comment). Signed-off-by: Arnaud Meukam <[email protected]>
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Done. I redeployed slack infra with the new images. |
@bartsmykla: 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. |
@bartsmykla @ameukam
kubernetes/test-infra#17461 switched the job to push images to community hosting, but nothing's actually been built yet
And our slack-infra deployment still uses the
gcr.io/kubernetes-tools
images (ref: https://cs.k8s.io/?q=kubernetes-tools&i=nope&files=&repos=kubernetes/k8s.io)Can we open a PR to slack-infra to cause new images builds, and update our deployment to use the new images?
/wg k8s-infra
The text was updated successfully, but these errors were encountered: