Change:
Hi, I'm following the document to build my kubernetes node, having both master and minion configured in same node and another minion node but I'm getting an error while I run the below command: $kubectl get nodes NAME LABELS STATUS .x.x Ready .x.y NotReady The 10.x.x.y is the separate minion node. I haven't set the bridge utils yet, is that the reason it's unable to fetch the state?
Have you looked in /var/log/kube-kubelet.* on 10.x.x.y for errors?
You must install bridge-util to get docker use flannel network. Maybe there are other problems. A look at the kubelet log will be helpful
Hi, thank you for the responses. So I reinstalled the ubuntu kubernetes setup of master and minion node. I have installed docker on both the nodes as it behaves as minion nodes. I have a new error this time. When I run the command 'KUBERNETES_PROVIDER=ubuntu ./kube-', it reads as cluster validation succeeded. Even it's able to fetch the node state that reads 'Ready'. The thing is when I issue the command 'kubectl get nodes' it comes as command not found. I'm issuing it in the directory that has kubectl but I have no clue what to do. All the services are up and running.
you forget something in my guide. The binary should be in cluster/ubuntu/binary directory.You can put it into your directory.So you can use
I did run the command in the specified directory. I have installed the same before and that time I didn't get this error and I could list the node states. The below is what I get: Kubernetes cluster is running. The master is running at: http://10.x.x.x. Using master 10.x.x.x line 356: create-kubeconfig: command not found
uhh, I'm a little confused, I need more info. Did you check the line 356 in
Yes, I did check it. It reads just like the document. verify-cluster detect-master export KUBEMASTERIP="${KUBEMASTERIP}:8080" export CONTEXT="ubuntu" create-kubeconfig }
Ah, I found it. Because someone has the code and merged it it's broken.I will figure it how to fix it soon
A quick question, I installed and configured kubernetes files yesterday and it read everything was done i.e the environment is up and running. If I want to set up from scratch what do I do? That is from getting repository and configuring files, bringing up services. I already have my services running which can be brought down by kube- If I comment out the 'create-kubeconfig' from I'm able to see the command fetching the nodes but kubectl doesn't work. It gives as unknown command.
I don't understand... what do you mean " That is from getting repository and all that"??
Apologies, I broke this with . Sending fix now.
I am going to fix it today so leave it to you
The issue of kube- seems to be fixed by adding 2 lines to the code file though I'm still facing the issue where I'm unable to list the nodes by using 'kubectl get nodes'. I'm issuing this command in /kubernetes/cluster/ubuntu/binaries where the kubectl is located. This is what I have: Kubernetes cluster is running. The master is running at: http://10.x.x.x Using master 10.x.x.x ... calling validate-cluster Found 2 nodes. NAME LABELS STATUS 1 10.x.x.x Ready 2 10.x.x.y Ready Validate output: NAME STATUS MESSAGE ERROR controller-manager Healthy ok nil scheduler Healthy ok nil etcd-0 Healthy {"action":"get","node":{"dir":true,"nodes":[{"key":"/registry","dir":true,"modifiedIndex":3,"createdIndex":3},{"key":"","dir":true,"modifiedIndex":8,"createdIndex":8}]}} nil Cluster validation succeeded Done, listing cluster services: Kubernetes master is running at http://10.x.x.x:8080 When I issue the command: $ kubectl get nodes kubectl: command not found
Another thing here is previously when I issued the command 'ifconfig' I was able to see my docker network but once I ran the 'kube-' command the docker network wasn't present on both the master and minion node but only the flannel network was .
You need to put the binary somewhere on your path. Distro-specific binaries are included in the , or you can build it from the repo by running .
I ran the command in /kubernetes/cluster/ubuntu/binaries and also tried by moving the kubectl to a different PATH. I ran the command in the /kubernetes/hack directory but I' facing error there. $ ./build- Can't find 'go' in PATH, please fix and retry.See for installation instructions. !!! Error in
It seems the changes to ubuntu was not enough. Other things will fail. I will try to fix it today.
Hi, is there another way to fix the kubectl command issue here.
According to this was (actually-for-real-this-time) fixed with . Have you tried it with a recent build?
yeah , I confirmed May the force be with you
I followed the following steps: $ wget $ chmod +x kubectl $ mv kubectl /usr/local/bin/ And then I executed the command: $ kubectl get nodes NAME LABELS STATUS .x.x NotReady .x.y NotReady I'm confused right now. When I ran the command kube- the final steps of it read like this: Using master 10.x.x.x ... calling validate-cluster Found 2 nodes. NAME LABELS STATUS 1 10.x.x.x Ready 2 10.x.x.y Ready Validate output: NAME STATUS MESSAGE ERROR controller-manager Healthy ok nil scheduler Healthy ok nil etcd-0 Healthy {"action":"get","node":{"dir":true,"nodes":[{"key":"/registry","dir":true,"modifiedIndex":3,"createdIndex":3},{"key":"","dir":true,"modifiedIndex":8,"createdIndex":8}]}} nil Cluster validation succeeded Done, listing cluster services: Kubernetes master is running at http://10.x.x.x:8080 If the state is reading ready why is it giving NotReady state while I make use of kubectl command.
weird, never happend in my lab.Try to use a 0.18.2 kubectl if your server side is using 0.18.2.It should be located in cluster/ubuntu/binaries
Previously I had built the kubernetes repo and then had manually downloaded the kubectl, I re-did it by first manually downloading the kubectl and then building the kubernetes repo. I'm able to fetch the state that's reading ready state.

Discussion:
# A library of helper functions that each provider hosting Kubernetes must implement to use cluster/kube-*.sh scripts. set -e <ins> source "${KUBE_ROOT}/cluster/common.sh" </ins> SSH_OPTS="-oStrictHostKeyChecking=no -oUserKnownHostsFile=/dev/null -oLogLevel=ERROR" # use an array to record name and ip