-
Notifications
You must be signed in to change notification settings - Fork 46
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
Failed Connectivity Test For Service V2 ubuntu+podman #165
Comments
that should be the nodeport, if you do |
Nope I have to restart server so IP may change
Using EXTERNAL-IP
with the IP from cloud-provider-kind log
|
so you can not connect from your host to the containers? are they not running in the same vm? |
nope, |
can you ping or connect to the containers directly? |
ubuntu@oraclu:~$ podman ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6413cba1a05b docker.io/kindest/node@sha256:18fbefc20a7113353c7b75b5c869d7145a6abd6269154825872dc59c1329912e 3 days ago Up 10 minutes 127.0.0.1:33139->6443/tcp kind-control-plane
7510cef9716f docker.io/envoyproxy/envoy:v1.30.1 bash -c echo -en ... 9 minutes ago Up 9 minutes 0.0.0.0:41359->10000/tcp kindccm-JQR2TXKKQBRJNYZ4LUJ4TY4C2YAW4FANP7ZCY5PN @aojea could you please provide the commands for ping and connect ? |
nevermind @aojea, it worked Solution purge podman and install docker. For podman it may be required a few more pre configuration.
@aojea do you test this with podman, maybe I can help with setup of CI+podman in this project ;) let me know if this is welcome. |
Having CI sounds like a good idea, but |
The ticket is very similar to #143 but unfortunately was not clear how to solve it.
Please instruct me how to troubleshoot this and finally fix it.
I will open a followup PR to add troubleshoot.md to be referenced in readme for others as soon I fix this setup.
Background
OS
IP tables
Setup
Set load balancer
ubuntu@oraclu:~/src_kind$ kubectl apply -f loadbalancer_etp_local.yaml deployment.apps/policy-local created service/lb-service-local created
Query load balancer
Additional configurations
The text was updated successfully, but these errors were encountered: