No nodes when running kubectl get nodes

[uritwig]

kubectl get nodes return no nodes
also we cant create deployments
we get
Type Reason Age From Message

---

Warning FailedScheduling 3m (x176 over 53m) default-scheduler no nodes available to schedule pods

[scholzj]

When there are no nodes, there is nowhere to deploy. So the warning message makes sense. However, since the aws-minikube cluster consists of single node I'm not sure how do you get the information about the deployment. Could you send me the output of kubectl get nodes and kubectl get pods --all-namespaces`?

[asafbit]

Hi, I am working with @uritwig on the project.
Both commands (get nods and pods) returns No resources found.
I only see this:
> kubectl get namespaces
NAME STATUS AGE
default Active 12m
kube-public Active 12m
kube-system Active 12m

[scholzj]

This is really strange ... the aws-minikube deployment should always show single node which is basically both master and node. The way you have it where it partially works but shows no nodes is strange.

Does it give you No resources found even when you do kubectl get pods --all-namespaces or kubectl get pods --namespace=kube-system? It should return at least some of the system pods.

Also, are you running kubectl remotely from your PC? If yes, could you try if it gets better when you SSH into the AWS host and try to use kubectl there? You would need to do something like this:

ssh centos@your-aws-host
export KUBECONFIG=/home/centos/kubeconfig_ip
kubectl get nodes

[alcnsahin]

getting following error

[root@ip-*** centos]# export KUBECONFIG=/home/centos/kubeconfig_ip
[root@ip-*** centos]# kubectl get pods --all-namespaces
W1214 22:07:35.284616 1916 loader.go:223] Config not found: /home/centos/kubeconfig_ip
The connection to the server localhost:8080 was refused - did you specify the right host or port?
[root@ip-*** centos]#

also

/home/centos/kubeconfig_ip: No such file or directory

[scholzj]

If the kubeconfig file does not exist, the provisioning was either not finished yet (it can take several minutes after the Terraform deployment is complete). Or something went wrong. You can check the log from the setup script. I think it should be in somewhere in /var/log.