Aias00 opened a new pull request, #6361:
URL: https://github.com/apache/shenyu/pull/6361
## Summary
- wait for k8s ingress deployments to finish rollout before HTTP health
probes
- add bounded curl timeouts and shared healthcheck logic for k8s ingress
cases
- keep cluster diagnostics running after healthcheck failures and include
pod descriptions
## Root cause
The linked grpc ingress CI run timed out in `Wait for k8s Cluster Start up`
before tests started. The original healthcheck immediately curled
`localhost:30095/actuator/health` after applying the kind resources, without
waiting for deployment rollout and without per-request curl timeouts. When
startup was slow or the endpoint accepted a connection but did not respond, a
curl process could hang until the GitHub Actions 15-minute step timeout killed
the job.
## Verification
- `bash -n shenyu-integrated-test/k8s-ingress-healthcheck.sh
shenyu-integrated-test/shenyu-integrated-test-k8s-ingress-{grpc,http,apache-dubbo,websocket}/script/healthcheck.sh`
- `git diff --check`
- local fake `kubectl` + HTTP 200 success-path run
- local fake `kubectl` + unreachable-service failure-path run
## Not tested
- full GitHub Actions kind matrix run locally
--
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]