Skip to content
This repository has been archived by the owner on Apr 29, 2019. It is now read-only.

k8s services have 10.100.x.y addresses #50

Closed
wkharold opened this issue Mar 18, 2015 · 8 comments
Closed

k8s services have 10.100.x.y addresses #50

wkharold opened this issue Mar 18, 2015 · 8 comments

Comments

@wkharold
Copy link

After vagrant up the kubernetes and kubernetes-ro services IP fields are 10.100.0.2 and 10.100.0.1 respectively. Those addresses aren't pingable from either the host machine or from the master.
@pires
Copy link
Owner

pires commented Mar 18, 2015

Service addresses are never pingable. See more details about services here.

@pires
Copy link
Owner

pires commented Mar 18, 2015

Nonetheless, accessing read-only service with curl http://${KUBERNETES_RO_SERVICE_HOST}:${KUBERNETES_RO_SERVICE_PORT} is not possible in any of the nodes. Looking at it!

@pires
Copy link
Owner

pires commented Mar 19, 2015

Bug in Kubernetes 0.13.x. With 0.12.2 it works. See kubernetes/kubernetes#5647

@pires pires mentioned this issue Mar 19, 2015
Closed
@pires
Copy link
Owner

pires commented Mar 19, 2015

@wkharold try this KUBERNETES_VERSION=0.12.2 vagrant up and then re-test what you're doing.

@pires pires mentioned this issue Mar 19, 2015
Closed
@wkharold
Copy link
Author

@pires with KUBERNETES_VERSION=0.12.2 attempting to curl kubernetes-ro times out. Doing
iptables -t nat -L yields: https://gist.github.com/wkharold/bd2fc9065e2b9b7dc433

@pires
Copy link
Owner

pires commented Mar 19, 2015

@wkharold works here.

core@node-01 ~ $ curl http://10.100.0.1
{
  "paths": [
    "/api",
    "/api/v1beta1",
    "/api/v1beta2",
    "/healthz",
    "/logs/",
    "/metrics",
    "/static/",
    "/swagger-ui/",
    "/swaggerapi/",
    "/validate",
    "/version"
  ]
}

@wkharold
Copy link
Author

@pires yes, works for me as well on a minion, just not on the master. I assume that's working as designed. Thanks.

@pires
Copy link
Owner

pires commented Mar 19, 2015

@wkharold yes, kube-proxy is not running on the master, so it's expected not to access services.

@pires pires closed this as completed Mar 19, 2015
pires added a commit that referenced this issue Mar 19, 2015
@pires
kube-proxy is deprecating flag --ectd_servers in favor of --master.
4789a92 
Refs #50
AntonioMeireles added a commit to AntonioMeireles/kubernetes-vagrant-coreos-cluster that referenced this issue Mar 19, 2015
@AntonioMeireles
fix kube-proxy semantics for 0.13.x sanity...
8807fe9 
[re: pires/issues/50 ]
[re: kubernetes/kubernetes#5647 ]

Signed-off-by: António Meireles <antonio.meireles@reformi.st>
AntonioMeireles added a commit to AntonioMeireles/kubernetes-vagrant-coreos-cluster that referenced this issue Mar 19, 2015
@AntonioMeireles
fix kube-proxy semantics for 0.13.x sanity...
145de37 
[re: pires/issues/50 ]
[re: (probably too) pires#46 ]
[re: kubernetes/kubernetes#5647 ]

Signed-off-by: António Meireles <antonio.meireles@reformi.st>
AntonioMeireles added a commit to AntonioMeireles/kubernetes-vagrant-coreos-cluster that referenced this issue Mar 19, 2015
@AntonioMeireles
fix kube-proxy semantics for 0.13.x sanity...
e200539 
[re: pires#50 ]
[re: (probably too) pires#46 ]
[re: kubernetes/kubernetes#5647 ]

Signed-off-by: António Meireles <antonio.meireles@reformi.st>
zutherb pushed a commit to zutherb/kubernetes-vagrant-coreos-cluster that referenced this issue Mar 28, 2015
Merge branch 'master' of git://github.com/pires/kubernetes-vagrant-co…
d776b6e 
…reos-cluster into pires-master

* 'master' of git://github.com/pires/kubernetes-vagrant-coreos-cluster: (35 commits)
  Fixes pires#51
  Allow for running privileged containers.
  Warning, only Kubernetes 0.13.x or newer is currently supported (and working).
  Removing etcd debugging stuff in order to simplify things.
  Ignoring bad SSL certificates when downloading kubectl.
  Fixing typos.
  Kubernetes upgraded to 0.13.2.
  kube-proxy is deprecating flag --ectd_servers in favor of --master. Refs pires#50
  Reverted to Kubernetes 0.12.2 since 0.13.x has broken services iptables rules. See kubernetes/kubernetes#5647
  Added waiter for Kubernetes API server before starting kube-proxy and kubelet.
  Latest Kubernetes version is really the latest tested, so 0.13.1 now.
  Desperate attempt at fixing so many issues that were brought by what we thought were smart moves. Sorry for that! Removing dockerized etcd 2.x Removing dockerized flannel Master node doesn't need to rely on its own dockercache for pulling images, for now. Refs pires#46 pires#47 pires#32
  Added more hypervisor related documentation love, namely removing DHCP from Virtualbox. Fixes pires#45
  Removed incompatible Docker flags because of bad merge.
  drop unneeded nfs related cruft.
  docker-cache container now restarts on failure. Refs pires#40
  only start docker in the minion nodes after the master's docker-cache is up.
  adding workaround for docker-archive/docker-registry#892
  rollback 182252c. just default kubernetes to latest stable release.
  fix pires#36 - docker could start before flanneld
  ...
zutherb pushed a commit to zutherb/kubernetes-vagrant-coreos-cluster that referenced this issue Mar 28, 2015
Merge branch 'pires-master'
6cb593a 
* pires-master: (35 commits)
  Fixes pires#51
  Allow for running privileged containers.
  Warning, only Kubernetes 0.13.x or newer is currently supported (and working).
  Removing etcd debugging stuff in order to simplify things.
  Ignoring bad SSL certificates when downloading kubectl.
  Fixing typos.
  Kubernetes upgraded to 0.13.2.
  kube-proxy is deprecating flag --ectd_servers in favor of --master. Refs pires#50
  Reverted to Kubernetes 0.12.2 since 0.13.x has broken services iptables rules. See kubernetes/kubernetes#5647
  Added waiter for Kubernetes API server before starting kube-proxy and kubelet.
  Latest Kubernetes version is really the latest tested, so 0.13.1 now.
  Desperate attempt at fixing so many issues that were brought by what we thought were smart moves. Sorry for that! Removing dockerized etcd 2.x Removing dockerized flannel Master node doesn't need to rely on its own dockercache for pulling images, for now. Refs pires#46 pires#47 pires#32
  Added more hypervisor related documentation love, namely removing DHCP from Virtualbox. Fixes pires#45
  Removed incompatible Docker flags because of bad merge.
  drop unneeded nfs related cruft.
  docker-cache container now restarts on failure. Refs pires#40
  only start docker in the minion nodes after the master's docker-cache is up.
  adding workaround for docker-archive/docker-registry#892
  rollback 182252c. just default kubernetes to latest stable release.
  fix pires#36 - docker could start before flanneld
  ...
Hikariii pushed a commit to Hikariii/kubernetes-vagrant-coreos-cluster that referenced this issue May 1, 2015
@pires
kube-proxy is deprecating flag --ectd_servers in favor of --master.
6d49604 
Refs pires#50
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wkharold @pires