Aias00 commented on PR #6361: URL: https://github.com/apache/shenyu/pull/6361#issuecomment-4645230131
Second follow-up after monitoring the new run: the kubectl compatibility issue is gone. The next failure was in `shenyu-integrated-test-k8s-ingress-apache-dubbo`, where the helper reached the bounded curl loop and `30095` became healthy, but `31187` stayed unreachable. Root cause from the diagnostic dump: the Dubbo example pod was being restarted by kubelet because its liveness probe hit `localhost:8081/actuator/health`, while the app and service use port `8011`. I pushed `e2d530051` to align that probe with `8011`. The SOFA k8s example had the same stale `8081` probe while serving on `28011`, so that probe is aligned too. Local verification: - `git diff --check` for the changed manifests - Ruby YAML parsing for the changed manifests The local environment has no kube-apiserver, so `kubectl apply --dry-run=client` cannot complete here; the PR CI run is the end-to-end validation. -- 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]
