search

rootsongjc / kubernetes-vagrant-centos-cluster

Setting up a distributed Kubernetes cluster along with Istio service mesh locally with Vagrant and VirtualBox, only PoC or Demo use.
https://jimmysong.io
Apache License 2.0
1.93k stars 594 forks source link

unable to recognize "STDIN" #70

Closed lidenis closed 5 years ago

lidenis commented 5 years ago

Environment

What I did?

I put the downloaded file kubernetes-client-linux-amd64.tar.gz and kubernetes-server-linux-amd64.tar.gz to the root folder and run vagrant up. in last step to for node3, I got the following error. seems the cluster connection haven't been established and the dashboard can't be opened:

node3: kubernetes/addons/
    node3: configure node3
    node3: Created symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /usr/lib/systemd/system/kubelet.service.
    node3: Created symlink from /etc/systemd/system/multi-user.target.wants/kube-proxy.service to /usr/lib/systemd/system/kube-proxy.service.
    node3: deploy coredns
    node3: unable to recognize "STDIN": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: connect: no route to host
    node3: unable to recognize "STDIN": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: connect: no route to host
    node3: unable to recognize "STDIN": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: connect: no route to host
    node3: unable to recognize "STDIN": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: connect: no route to host
    node3: unable to recognize "STDIN": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: i/o timeout
    node3: unable to recognize "STDIN": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: i/o timeout
    node3: /home/vagrant
    node3: deploy kubernetes dashboard
    node3: unable to recognize "/vagrant/addon/dashboard/kubernetes-dashboard.yaml": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: i/o timeout
    node3: unable to recognize "/vagrant/addon/dashboard/kubernetes-dashboard.yaml": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: i/o timeout
    node3: unable to recognize "/vagrant/addon/dashboard/kubernetes-dashboard.yaml": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: i/o timeout
    node3: unable to recognize "/vagrant/addon/dashboard/kubernetes-dashboard.yaml": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: i/o timeout
    node3: unable to recognize "/vagrant/addon/dashboard/kubernetes-dashboard.yaml": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: i/o timeout
    node3: unable to recognize "/vagrant/addon/dashboard/kubernetes-dashboard.yaml": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: i/o timeout
    node3: create admin role token
    node3: unable to recognize "/vagrant/yaml/admin-role.yaml": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: connect: no route to host
    node3: unable to recognize "/vagrant/yaml/admin-role.yaml": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: connect: no route to host
    node3: the admin role token is:
    node3: Unable to connect to the server: dial tcp 172.17.8.101:6443: connect: no route to host
    node3: Unable to connect to the server: dial tcp 172.17.8.101:6443: connect: no route to host
    node3: login to dashboard with the above token
    node3: Unable to connect to the server: dial tcp 172.17.8.101:6443: i/o timeout
    node3: https://172.17.8.101:
    node3: install traefik ingress controller
    node3: unable to recognize "/vagrant/addon/traefik-ingress/ingress.yaml": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: i/o timeout
    node3: unable to recognize "/vagrant/addon/traefik-ingress/traefik-rbac.yaml": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: i/o timeout
    node3: unable to recognize "/vagrant/addon/traefik-ingress/traefik.yaml": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: i/o timeout
    node3: unable to recognize "/vagrant/addon/traefik-ingress/traefik.yaml": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: i/o timeout
    node3: unable to recognize "/vagrant/addon/traefik-ingress/traefik.yaml": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: i/o timeout
    node3: Configure Kubectl to autocomplete
QQ20190422-173447@2x

Messages

Logs or error messages.

rootsongjc commented 5 years ago

You can check the kube-apiserver first to figure out if it is work.

rootsongjc commented 5 years ago

The codes had been updated, please try the latest version.