I find this really weird. Re-created the cluster today, still the same problem. If you are interested in the kubernetes setup I have it added it on github: https://github.com/mastoj/kubernetes_hello_world, it’s the eventstore-rc3.yaml that is currently used to create the replication controller. I have attached both the gossip response and a the log output for the settings I’m using now (pasted after the gossip sample). I do get a gossip response from all the nodes from the container I have running to make queries against the other nodes. The gossip response looks like this for one of the nodes:
{
“members”: [
{
“instanceId”: “00000000-0000-0000-0000-000000000000”,
“timeStamp”: “2016-01-02T21:14:00.944213Z”,
“state”: “Manager”,
“isAlive”: false,
“internalTcpIp”: “10.246.32.9”,
“internalTcpPort”: 2113,
“internalSecureTcpPort”: 0,
“externalTcpIp”: “10.246.32.9”,
“externalTcpPort”: 2113,
“externalSecureTcpPort”: 0,
“internalHttpIp”: “10.246.32.9”,
“internalHttpPort”: 2113,
“externalHttpIp”: “10.246.32.9”,
“externalHttpPort”: 2113,
“lastCommitPosition”: -1,
“writerCheckpoint”: -1,
“chaserCheckpoint”: -1,
“epochPosition”: -1,
“epochNumber”: -1,
“epochId”: “00000000-0000-0000-0000-000000000000”,
“nodePriority”: 0
},
{
“instanceId”: “00000000-0000-0000-0000-000000000000”,
“timeStamp”: “2016-01-02T21:14:01.241319Z”,
“state”: “Manager”,
“isAlive”: false,
“internalTcpIp”: “10.246.32.8”,
“internalTcpPort”: 2113,
“internalSecureTcpPort”: 0,
“externalTcpIp”: “10.246.32.8”,
“externalTcpPort”: 2113,
“externalSecureTcpPort”: 0,
“internalHttpIp”: “10.246.32.8”,
“internalHttpPort”: 2113,
“externalHttpIp”: “10.246.32.8”,
“externalHttpPort”: 2113,
“lastCommitPosition”: -1,
“writerCheckpoint”: -1,
“chaserCheckpoint”: -1,
“epochPosition”: -1,
“epochNumber”: -1,
“epochId”: “00000000-0000-0000-0000-000000000000”,
“nodePriority”: 0
},
{
“instanceId”: “b3c8faf5-37de-4f9d-853e-2db6a560101c”,
“timeStamp”: “2016-01-02T21:17:50.330808Z”,
“state”: “Unknown”,
“isAlive”: true,
“internalTcpIp”: “10.246.32.8”,
“internalTcpPort”: 1112,
“internalSecureTcpPort”: 0,
“externalTcpIp”: “10.246.32.8”,
“externalTcpPort”: 1113,
“externalSecureTcpPort”: 0,
“internalHttpIp”: “10.246.32.8”,
“internalHttpPort”: 2112,
“externalHttpIp”: “10.246.32.8”,
“externalHttpPort”: 2113,
“lastCommitPosition”: -1,
“writerCheckpoint”: 0,
“chaserCheckpoint”: 0,
“epochPosition”: -1,
“epochNumber”: -1,
“epochId”: “00000000-0000-0000-0000-000000000000”,
“nodePriority”: 0
},
{
“instanceId”: “00000000-0000-0000-0000-000000000000”,
“timeStamp”: “2016-01-02T21:14:01.039863Z”,
“state”: “Manager”,
“isAlive”: false,
“internalTcpIp”: “10.246.32.7”,
“internalTcpPort”: 2113,
“internalSecureTcpPort”: 0,
“externalTcpIp”: “10.246.32.7”,
“externalTcpPort”: 2113,
“externalSecureTcpPort”: 0,
“internalHttpIp”: “10.246.32.7”,
“internalHttpPort”: 2113,
“externalHttpIp”: “10.246.32.7”,
“externalHttpPort”: 2113,
“lastCommitPosition”: -1,
“writerCheckpoint”: -1,
“chaserCheckpoint”: -1,
“epochPosition”: -1,
“epochNumber”: -1,
“epochId”: “00000000-0000-0000-0000-000000000000”,
“nodePriority”: 0
}
],
“serverIp”: “10.246.32.8”,
“serverPort”: 2112
}
``
Here are the logs as well. It looks like the nodes fails to resolve the dns, but when I do a nslookup from my test container I do get a response. It also says that gossip fails, but when make a request to /gossip I do get the response as pasted above.