Started by GitHub push by ti-chi-bot[bot]Started by GitHub push by ti-chi-bot[bot]00156721567244556445561.0243362433606889286628662162965b62be45a3ffdfe05ab1617f0eb2bf1d2b1e58565b62be45a3ffdfe05ab1617f0eb2bf1d2b1e585origin/main65b62be45a3ffdfe05ab1617f0eb2bf1d2b1e58565b62be45a3ffdfe05ab1617f0eb2bf1d2b1e585origin/main65b62be45a3ffdfe05ab1617f0eb2bf1d2b1e58565b62be45a3ffdfe05ab1617f0eb2bf1d2b1e585origin/mainhttps://github.com/PingCAP-QE/ci.githttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1629/artifactshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1629/changeshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1629/https://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1629/testsfalse#16294455643022seed #16291629falsefalse16293669896SUCCESS1776337937165https://do.pingcap.net/jenkins/job/seed/1629/default-wq6nwpipelines/ti-community-infra/test-prod/pod-prow_debug.yaml.ci/verify-k8s-pod-yaml.sh65b62be45a3ffdfe05ab1617f0eb2bf1d2b1e5851776337908000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comfix: skip kubectl client/server validation (#4530) ## Summary - auto-generate in-cluster kubeconfig from service account token/CA when no kubeconfig context exists in prow job pod - always run kubectl --dry-run=client and --dry-run=server with strict validation in .ci/verify-k8s-pod-yaml.sh - update pod-prow_debug pod yaml so this PR triggers pull-verify-k8s-pod-yaml for end-to-end verification - sync CI guide doc for the new behavior ## Validation - sh -n .ci/verify-k8s-pod-yaml.sh - mock kubectl run confirms config set-cluster/set-credentials/set-context and both apply --dry-run=client/server are invoked 2026-04-16 11:11:48 +000065b62be45a3ffdfe05ab1617f0eb2bf1d2b1e585fix: skip kubectl client/server validation (#4530)edit.ci/verify-k8s-pod-yaml.sheditpipelines/ti-community-infra/test-prod/pod-prow_debug.yamlgithttps://do.pingcap.net/jenkins/user/noreplynoreplynoreply