Closed xenithorb closed 7 years ago
On the bright side, you should be able to vagrant up
in the tests
directory and it will spin up two virtual machines, a master and a node, and follows through with the node add to master. As far as I can tell everything looks ok.
There are still idempotency problems with a second run due to "Start master node" and "Register nodes with master" not being idepotent tasks.
With this vagrant config (and simply executing vagrant up
) you get:
[vagrant@easy-kube-master ~]$ kubectl get nodes
NAME STATUS AGE
easy-kube-master Ready 1m
easy-kube-node Ready 31s
[vagrant@easy-kube-master ~]$ kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system etcd-easy-kube-master 1/1 Running 0 20s
kube-system kube-apiserver-easy-kube-master 1/1 Running 0 1m
kube-system kube-controller-manager-easy-kube-master 1/1 Running 0 1m
kube-system kube-discovery-982812725-qx7hi 1/1 Running 0 1m
kube-system kube-dns-2247936740-xfchi 0/3 ContainerCreating 0 54s
kube-system kube-proxy-amd64-4c9g6 1/1 Running 0 44s
kube-system kube-proxy-amd64-f2kly 1/1 Running 0 54s
kube-system kube-scheduler-easy-kube-master 1/1 Running 0 26s
kube-system weave-net-0ovp8 0/2 ContainerCreating 0 47s
kube-system weave-net-qzhlg 0/2 ContainerCreating 0 44s
:)
great that's all merged ill run against vagrant soon. thanks for your help!
Use the following instructions to fix up:
Thanks so much, sorry for the confusion.