Bug: logs / exec interactive for container with custom ports

[vsoch]

Hey @AkihiroSuda! I'm testing the new ports setup, and ran into a bug with respect to looking at logs and interactive shells:

$ kubectl  exec -it somaxconn -- bash
error: Internal error occurred: error sending request: Post "https://10.0.1.25:30031/exec/default/somaxconn/somaxconn?command=bash&input=1&output=1&tty=1": dial tcp 10.0.1.25:30031: connect: connection refused

To reproduce, just set custom ports and then try to look at logs. The same setup without custom ports works to show the logs.

[AkihiroSuda]

30031

Is this the port you explicitly specified as PORT_KUBELET?

[vsoch]

Is this the port you explicitly specified as PORT_KUBELET?

yes, I think so, if that is the port that populates that command.

[AkihiroSuda]

Can't repro this on the CI

• Test kubectl exec issue 357 #360