-
Notifications
You must be signed in to change notification settings - Fork 593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
e2e test TestDeployAllInOneDBLESS
fails on kind environment
#6317
Comments
Some initial investigation: The bug may brought by the port forward. In https://github.com/Kong/kubernetes-ingress-controller/actions/runs/10156183607/job/28084180522 I found the following logs in
The two containers are forwarded to the same port but different paths. While in our tests it receives 2 different ports:
So there maybe bugs in picking and receiving proxy ports in port forwarding. |
Recently
TestDeployAllInOneDBLESS
e2e test case running on kind environment fails on getting configuration from Kong gateway pods. The failure of dumping config is caused by port forwarding not work, like: https://github.com/Kong/kubernetes-ingress-controller/actions/runs/9902467231/job/27356436727.The same case running on GKE passed, and also it can run on local kind env. Also, https://github.com/Kong/kubernetes-ingress-controller/actions/runs/9902467231/job/27356450395 fails for the same reason.
So there maybe some issue on forwarding ports in kind env on the GH runners.
The text was updated successfully, but these errors were encountered: