Can't access pods behind service

12/1/2015

I'm attempting to access a WebSphere App Server I have running on Kubernetes, and I can't seem to be able to connect properly. I have a pod running behind a service that should connect it's admin console port to an external NodePort. Problem is it resets the connection every time I try. I had the same issue with an ssh port for another pod, but that was fixed when I fixed a Weave networking error. At this point, I can't tell if it's a Kubernetes or Weave error, or something else all together. Any help would be appreciated.

I'm running KubeV1.1.0 off the release-1.1 branch, Mesos 0.24.0, and Weave 1.0.1. My next step is to try a different version of K8s.

-- bradams
kubernetes
weave

1 Answer

12/1/2015

The Kubernetes release-1.1 branch was cut before the master branch started passing conformance tests on Mesos. A lot of work has been done since then to make Kubernetes on Mesos more usable. Not all of those changes/fixes have been backported/cherry-picked to fix the v1.1 release branch. It's probably a better idea to try using the code from master branch for the time being, at least while the kubernetes-mesos integration is in alpha. We hope future point releases will be more stable.

(I work on the Kubernetes-Mesos team at Mesosphere.)

-- KarlKFI
Source: StackOverflow