Started by GitHub push by ti-chi-bot[bot]0031517315171645681645681.008314831416961a565c5b0ab7e2c747c05834f6714225a7f8b0961a565c5b0ab7e2c747c05834f6714225a7f8b096origin/main1a565c5b0ab7e2c747c05834f6714225a7f8b0961a565c5b0ab7e2c747c05834f6714225a7f8b096origin/main1a565c5b0ab7e2c747c05834f6714225a7f8b0961a565c5b0ab7e2c747c05834f6714225a7f8b096origin/mainhttps://github.com/PingCAP-QE/ci.gitfalse#1696164568132442seed #16961696falsefalse16963684232SUCCESS1779185306715https://do.pingcap.net/jenkins/job/seed/1696/default-3pm3jprow-jobs/ti-community-infra/prow/presubmits.yaml1a565c5b0ab7e2c747c05834f6714225a7f8b0961779185258000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comfix(prow): update kubekins image for prow jobs (#4601) ## What Update the ti-community-infra/prow presubmit jobs to use the current Artifact Registry kubekins image: - `us-central1-docker.pkg.dev/k8s-staging-test-infra/images/kubekins-e2e:latest-master` This replaces the old GCR tag that now returns `MANIFEST_UNKNOWN` and causes `pull-test` / `pull-verify` to fail with `ImagePullBackOff`. ## Jobs updated - `pull-test` - `pull-build-images` - `pull-verify` ## Verification - Parsed `prow-jobs/ti-community-infra/prow/presubmits.yaml` with Python YAML - Verified the new image manifest endpoint returns HTTP 200 - Ran `.ci/update-prow-job-kustomization.sh` and confirmed no generated changes 2026-05-19 10:07:38 +00001a565c5b0ab7e2c747c05834f6714225a7f8b096fix(prow): update kubekins image for prow jobs (#4601)editprow-jobs/ti-community-infra/prow/presubmits.yamlgithttps://do.pingcap.net/jenkins/user/noreplynoreply