Migrate kops-ci version marker consumption to k8s-staging-kops #32896
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.
ref: kubernetes/kops#16637 kubernetes/k8s.io#2625
These buckets contain identical latest-ci.txt markers and are publicly readable so we can migrate jobs to read from the community-owned k8s-staging-kops bucket.
Note this doesn't actually move any jobs to the new prow clusters - these jobs are either already migrated or blocked for unrelated reasons.
/cc @hakman @upodroid