BobSong-dev opened a new pull request, #7427: URL: https://github.com/apache/shenyu/pull/7427
### Background The Dubbo ingress setup applies the ZooKeeper Deployment and immediately waits for Pods matching its label. Kubernetes creates those Pods asynchronously, so `kubectl wait` can fail with `no matching resources found` before a Pod exists. This happened in the Kubernetes Dubbo job for #7424, before ShenYu deployment or business tests started. The same setup script remains in master. ### Changes - Wait for the named ZooKeeper Deployment to finish rolling out, with an explicit 120-second timeout. Preserve nonzero failures and stop before subsequent deployments if readiness fails. - Add five Bash regression cases covering delayed Pod creation, rollout timeout, Forbidden responses, manifest application failure and image loading failure. - Run the regression script only in the Dubbo ingress matrix branch, before installing Kubernetes. ### Verification - Both scripts passed `bash -n`; all five Bash regression cases passed in Windows Git Bash and an existing RISC-V Linux container (repeated cases, not ten distinct tests). The same delayed-Pod case failed against the original master script with `no matching resources found`. - Five controlled API checks passed with Windows kubectl v1.24.14, matching the workflow's client version. Earlier v1.36.1 checks remain separate evidence. - Five readiness checks passed on an isolated real kind v0.14.0 / Kubernetes v1.21.1 cluster using kubectl v1.24.14 and the repository's ZooKeeper manifest. A temporary Pod quota reproduced the old missing-Pod failure; the production 120-second rollout command remained pending until Pods could be created and then succeeded. Already-ready rollout, actual ZooKeeper server status and bounded failure (2-second negative-case limit) also passed. The existing client/server version-skew warning was retained. - Workflow YAML and matrix/step assertions passed; `git diff --cached --check` passed. - Root-only Maven Wrapper `validate` and `apache-rat:check` passed: zero Checkstyle violations and zero unapproved/unknown licenses. - Not run: the complete Dubbo ingress business integration test or full-project Java tests. Remote CI results are not implied by local verification. Earlier image-pull EOF failures were resolved; no global Docker or kubeconfig settings were changed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
