-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
3
-
False
-
-
False
-
---
-
---
-
-
No
We are currently using an intermediate registry to pull the prow images: https://github.com/kubevirt/project-infra/blob/2aa7c952a9ae348c2c4b51e87c803b8a45c0730f/github/ci/prow-deploy/kustom/base/manifests/test_infra/current/deck_deployment.yaml#L41
Work to push towards registry.k8s.io is still ongoing: https://kubernetes.slack.com/archives/CDECRSC5U/p1727774117129299
At some point push target is expected to change here: https://github.com/kubernetes-sigs/prow/blob/8442fff47c208254cf206fca5dbfbf6191828c91/cloudbuild.yaml#L13
We then need to adapt the hack/bump-prow.sh and the image references after the publishing of images for prow has moved to registry.k8s.io
Link to prow bump mechanism: https://github.com/kubevirt/project-infra/blob/2aa7c952a9ae348c2c4b51e87c803b8a45c0730f/hack/bump-prow.sh#L23
- clones
-
CNV-40982 Adapt prow autoupdate automation after prow images have been moved from gcr.io to registry.k8s.io
- Closed