Update k8s-staging-test-infra GCR images as needed #34036
Merged
+2,541
−2,541
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@k8s-infra-ci-robot: GitHub didn't allow me to request PR reviews from the following users: k8s-infra-ci-robot. Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs. 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-sigs/prow repository. |
k8s-ci-robot
added
cncf-cla: yes
k8s-infra-ci-robot
force-pushed
the
prowjobs-autobump
branch
from
68eac23 to
1910de2
Compare
k8s-infra-ci-robot
force-pushed
the
prowjobs-autobump
branch
2 times, most recently
from
fc64182 to
da6c917
Compare
|
@dims can we merge this PR or what else is missing? Thank you. |
|
@mainred monday please, not many of us are around to monitor if something breaks |
k8s-infra-ci-robot
force-pushed
the
prowjobs-autobump
branch
4 times, most recently
from
db7334b to
230404d
Compare
…nd k8s-staging-test-infra AR images and k8s-staging-apisnoop-test-infra and k8s-staging-apisnoop-apisnoop No gcr.io/k8s-testimages/ changes. Multiple distinct gcr.io/k8s-staging-test-infra changes: Commits | Dates | Images --- | --- | --- kubernetes/test-infra@ff9ecc4...fe22c54 | 2024‑10‑15 → 2024‑12‑24 | image-builder kubernetes/test-infra@d4b51bc...5dc092c | 2024‑12‑18 → 2024‑12‑29 | kubekins-e2e(1.29), kubekins-e2e(1.30), kubekins-e2e(1.31), kubekins-e2e(1.32), kubekins-e2e(go-canary), kubekins-e2e(master) kubernetes/test-infra@93c4db6...5dc092c | 2024‑12‑18 → 2024‑12‑29 | commenter, configurator, issue-creator, label_sync No us-central1-docker.pkg.dev/k8s-staging-test-infra/images changes. No gcr.io/k8s-staging-apisnoop/ changes. No gcr.io/k8s-staging-apisnoop/ changes.
k8s-infra-ci-robot
force-pushed
the
prowjobs-autobump
branch
from
230404d to
d32d189
Compare
k8s-ci-robot
added
area/provider/aws
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: k8s-infra-ci-robot The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
area/provider/vmware
k8s-ci-robot
added
sig/api-machinery
dims
added
the
skip-review
|
@k8s-infra-ci-robot: Updated the
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-sigs/prow repository. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No gcr.io/k8s-testimages/ changes.
Multiple distinct gcr.io/k8s-staging-test-infra changes:
No us-central1-docker.pkg.dev/k8s-staging-test-infra/images changes.
No gcr.io/k8s-staging-apisnoop/ changes.
No gcr.io/k8s-staging-apisnoop/ changes.
/cc
/cc @dims