pipelines(tiflash): migrate container images from hub.pingcap.net to us-docker.pkg.dev

[Copilot]

hub.pingcap.net is an internal-only registry. All 39 pod YAML files across pipelines/pingcap/tiflash/ hardcoded image pulls from it, making jobs inaccessible from cloud environments.

Changes

• All tiflash pod YAMLs (latest, release-6.1 through release-9.0-beta): replaced hub.pingcap.net/ with us-docker.pkg.dev/pingcap-testing-account/hub/ — the same GCP Artifact Registry already used as OCI_ARTIFACT_HOST in the Groovy pipeline scripts

Images migrated (97 references across 39 files):

• tiflash/tiflash-llvm-base:<tag> — runner/build container
• jenkins/ks3util — S3 utility sidecar
• jenkins/network-multitool — network diagnostics sidecar
• jenkins/docker:20.10.24[-dind] — integration test Docker (release-6.x only)
• jenkins/docker:build-essential-java — integration test Docker (release-7.x+)

Before/after:

# Before
image: "hub.pingcap.net/tiflash/tiflash-llvm-base:rocky8-llvm-17.0.6-v2"
image: hub.pingcap.net/jenkins/ks3util

# After
image: "us-docker.pkg.dev/pingcap-testing-account/hub/tiflash/tiflash-llvm-base:rocky8-llvm-17.0.6-v2"
image: us-docker.pkg.dev/pingcap-testing-account/hub/jenkins/ks3util

This aligns pod YAML image sources with the registry already used by the Groovy pipelines for OCI artifact downloads.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>hub registry: migrate images for pingcap/tiflash</issue_title>
<issue_description>Replace hub.pingcap.net image pulls/pushes for pingcap/tiflash with a cloud-accessible registry.

Acceptance criteria:

• No hub.pingcap.net references in jobs/pipelines for pingcap/tiflash
• Image registry endpoints documented and validated
  </issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes hub registry: migrate images for pingcap/tiflash #4223

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[ti-chi-bot]

Hi @Copilot. Thanks for your PR.

I'm waiting for a PingCAP-QE member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from wuhuizuo. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• pipelines/pingcap/tiflash/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment