No nodes available in AWS EKSAmazon Kubernetes AWS-EKS is not getting created properly or not synched with kubectlCan't access Heapster's InfluxDB port 8083no pods monitor information in kubernetes(heapster, influxdb, grafana)issue on arm64: no endpoints,code:503unable to access kubernetes dashboard via tokenCan't resolve monitoring-influxdb on Kubernetes with heapster and kube-dnsNodePort services not available on all nodesGrafana shows dead kubernetes pods from influxdbPods stay in ContainerCreating state with “Failed create pod sandbox” messageCan change clusterip to nodeport command line without editor?Kubectl top nodes/pods works correctly but kubernetes dashboard doesn't show the cpu/memory graphs
Will 700 more planes a day fly because of the Heathrow expansion?
Word for Food that's Gone 'Bad', but is Still Edible?
What does 'made on' mean here?
Are there any of the Children of the Forest left, or are they extinct?
Refinish or replace an old staircase
A factorization game
Is there an idiom that support the idea that "inflation is bad"?
Causes of bimodal distributions when bootstrapping a meta-analysis model
Point of the Dothraki's attack in GoT S8E3?
Where is the documentation for this ex command?
Has a commercial or military jet bi-plane ever been manufactured?
Can FreeNAS zfs send to a Linux machine?
How can I support myself financially as a 17 year old with a loan?
Does it make sense for a function to return an rvalue reference?
Nominativ or Akkusativ
Find the cheapest shipping option based on item weight
What exactly are the `size issues' preventing formation of presheaves being a left adjoint to some forgetful functor?
How can internet speed be 10 times slower without a router than when using a router?
How to increase the size of the cursor in Lubuntu 19.04?
Why aren't nationalizations in Russia described as socialist?
How to use dependency injection and avoid temporal coupling?
In Stroustrup's example, what does this colon mean in `return 1 : 2`? It's not a label or ternary operator
How can I get people to remember my character's gender?
Why is "breaking the mould" positively connoted?
No nodes available in AWS EKS
Amazon Kubernetes AWS-EKS is not getting created properly or not synched with kubectlCan't access Heapster's InfluxDB port 8083no pods monitor information in kubernetes(heapster, influxdb, grafana)issue on arm64: no endpoints,code:503unable to access kubernetes dashboard via tokenCan't resolve monitoring-influxdb on Kubernetes with heapster and kube-dnsNodePort services not available on all nodesGrafana shows dead kubernetes pods from influxdbPods stay in ContainerCreating state with “Failed create pod sandbox” messageCan change clusterip to nodeport command line without editor?Kubectl top nodes/pods works correctly but kubernetes dashboard doesn't show the cpu/memory graphs
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I am trying to setup an AWS EKS cluster and followed the instructions in https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html. But while trying to setup the dashboard I realized I do not have any nodes and don't know why.
Yes, I made sure that the CloudFormation stack for my nodes has the exact name of my EKS cluster and I applied the aws-auth-cm.yaml with the stacks NodeInstanceRole.
A similar question came up here Amazon Kubernetes AWS-EKS is not getting created properly or not synched with kubectl but there is no usable information there.
Here is some info:
$ kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP <IP> <none> 443/TCP 11d
$ kubectl get all --namespace=default
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP <IP> <none> 443/TCP 11d
$ kubectl get nodes --namespace=kube-system
No resources found.
get nodes gives No resources found for any of the namespaces I have: kube-system, kube-public, or default.
$ kubectl get all --namespace=kube-system
NAME READY STATUS RESTARTS AGE
pod/heapster-7ff8d6bf9f-qv56t 0/1 Pending 0 44m
pod/kube-dns-69ff9fcd66-ls9w7 0/3 Pending 0 11d
pod/kubernetes-dashboard-669f9bbd46-xthpq 0/1 Pending 0 45m
pod/monitoring-influxdb-cc95575b9-qjk4r 0/1 Pending 0 44m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/heapster ClusterIP <IP> <none> 80/TCP 44m
service/kube-dns ClusterIP <IP> <none> 53/UDP,53/TCP 11d
service/kubernetes-dashboard ClusterIP <IP> <none> 443/TCP 45m
service/monitoring-influxdb ClusterIP <IP> <none> 8086/TCP 44m
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/aws-node 0 0 0 0 0 <none> 11d
daemonset.apps/kube-proxy 0 0 0 0 0 <none> 11d
daemonset.apps/nvidia-device-plugin-daemonset 0 0 0 0 0 <none> 34m
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
deployment.apps/heapster 1 1 1 0 44m
deployment.apps/kube-dns 1 1 1 0 11d
deployment.apps/kubernetes-dashboard 1 1 1 0 45m
deployment.apps/monitoring-influxdb 1 1 1 0 44m
NAME DESIRED CURRENT READY AGE
replicaset.apps/heapster-7ff8d6bf9f 1 1 0 44m
replicaset.apps/kube-dns-69ff9fcd66 1 1 0 11d
replicaset.apps/kubernetes-dashboard-669f9bbd46 1 1 0 45m
replicaset.apps/monitoring-influxdb-cc95575b9 1 1 0 44m
UPDATE:
After I send a Kubernetes API call from my backend to launch some pods I get the following output (kubectl get jobs is similar) but still no actual instances spin up and the jobs never execute.
$ kubectl get svc
kubernetes ClusterIP <IP> <none> 443/TCP 14d
svc-3d1de3dc-7ca1-1f83-7a5e-548e5c5b4d12 NodePort <IP> <none> 8082:32433/TCP,8081:30374/TCP,8096:31178/TCP,8083:31067/TCP 1m
svc-3d1de3dc-7ca1-1f83-7a5e-548e5c5b4d12-sut0 ClusterIP <IP> <none> 50001/TCP 1m
svc-7429ae6b-6f4b-012b-2d93-7c244109090b NodePort <IP> <none> 8082:30736/TCP,8081:31272/TCP,8096:30857/TCP,8083:30949/TCP 1m
svc-7429ae6b-6f4b-012b-2d93-7c244109090b-sut0 ClusterIP <IP> <none> 50001/TCP 1m
svc-89e81309-f6e4-21b1-ab8d-ecfb74d08010 NodePort <IP> <none> 8082:32072/TCP,8081:31236/TCP,8096:30000/TCP,8083:31257/TCP 1m
svc-89e81309-f6e4-21b1-ab8d-ecfb74d08010-sut0 ClusterIP <IP> <none> 50001/TCP 1m
svc-c196e61f-098e-7b10-9d05-6d06ccbdbb9f NodePort <IP> <none> 8082:32541/TCP,8081:30305/TCP,8096:31738/TCP,8083:31846/TCP 1m
svc-c196e61f-098e-7b10-9d05-6d06ccbdbb9f-sut0 ClusterIP <IP> <none> 50001/TCP 1m
amazon-web-services
kubernetes amazon-eks aws-eks asked Mar 22 at 23:56
kilgoretroutkilgoretrout
1,15421732
add a comment |
I am trying to setup an AWS EKS cluster and followed the instructions in https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html. But while trying to setup the dashboard I realized I do not have any nodes and don't know why.
Yes, I made sure that the CloudFormation stack for my nodes has the exact name of my EKS cluster and I applied the aws-auth-cm.yaml with the stacks NodeInstanceRole.
A similar question came up here Amazon Kubernetes AWS-EKS is not getting created properly or not synched with kubectl but there is no usable information there.
Here is some info:
$ kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP <IP> <none> 443/TCP 11d
$ kubectl get all --namespace=default
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP <IP> <none> 443/TCP 11d
$ kubectl get nodes --namespace=kube-system
No resources found.
get nodes gives No resources found for any of the namespaces I have: kube-system, kube-public, or default.
$ kubectl get all --namespace=kube-system
NAME READY STATUS RESTARTS AGE
pod/heapster-7ff8d6bf9f-qv56t 0/1 Pending 0 44m
pod/kube-dns-69ff9fcd66-ls9w7 0/3 Pending 0 11d
pod/kubernetes-dashboard-669f9bbd46-xthpq 0/1 Pending 0 45m
pod/monitoring-influxdb-cc95575b9-qjk4r 0/1 Pending 0 44m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/heapster ClusterIP <IP> <none> 80/TCP 44m
service/kube-dns ClusterIP <IP> <none> 53/UDP,53/TCP 11d
service/kubernetes-dashboard ClusterIP <IP> <none> 443/TCP 45m
service/monitoring-influxdb ClusterIP <IP> <none> 8086/TCP 44m
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/aws-node 0 0 0 0 0 <none> 11d
daemonset.apps/kube-proxy 0 0 0 0 0 <none> 11d
daemonset.apps/nvidia-device-plugin-daemonset 0 0 0 0 0 <none> 34m
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
deployment.apps/heapster 1 1 1 0 44m
deployment.apps/kube-dns 1 1 1 0 11d
deployment.apps/kubernetes-dashboard 1 1 1 0 45m
deployment.apps/monitoring-influxdb 1 1 1 0 44m
NAME DESIRED CURRENT READY AGE
replicaset.apps/heapster-7ff8d6bf9f 1 1 0 44m
replicaset.apps/kube-dns-69ff9fcd66 1 1 0 11d
replicaset.apps/kubernetes-dashboard-669f9bbd46 1 1 0 45m
replicaset.apps/monitoring-influxdb-cc95575b9 1 1 0 44m
UPDATE:
After I send a Kubernetes API call from my backend to launch some pods I get the following output (kubectl get jobs is similar) but still no actual instances spin up and the jobs never execute.
$ kubectl get svc
kubernetes ClusterIP <IP> <none> 443/TCP 14d
svc-3d1de3dc-7ca1-1f83-7a5e-548e5c5b4d12 NodePort <IP> <none> 8082:32433/TCP,8081:30374/TCP,8096:31178/TCP,8083:31067/TCP 1m
svc-3d1de3dc-7ca1-1f83-7a5e-548e5c5b4d12-sut0 ClusterIP <IP> <none> 50001/TCP 1m
svc-7429ae6b-6f4b-012b-2d93-7c244109090b NodePort <IP> <none> 8082:30736/TCP,8081:31272/TCP,8096:30857/TCP,8083:30949/TCP 1m
svc-7429ae6b-6f4b-012b-2d93-7c244109090b-sut0 ClusterIP <IP> <none> 50001/TCP 1m
svc-89e81309-f6e4-21b1-ab8d-ecfb74d08010 NodePort <IP> <none> 8082:32072/TCP,8081:31236/TCP,8096:30000/TCP,8083:31257/TCP 1m
svc-89e81309-f6e4-21b1-ab8d-ecfb74d08010-sut0 ClusterIP <IP> <none> 50001/TCP 1m
svc-c196e61f-098e-7b10-9d05-6d06ccbdbb9f NodePort <IP> <none> 8082:32541/TCP,8081:30305/TCP,8096:31738/TCP,8083:31846/TCP 1m
svc-c196e61f-098e-7b10-9d05-6d06ccbdbb9f-sut0 ClusterIP <IP> <none> 50001/TCP 1m
amazon-web-services
kubernetes amazon-eks aws-eks asked Mar 22 at 23:56
kilgoretroutkilgoretrout
1,15421732
2
Has CloudFormation created the ECS instances for your nodes? If no, they are missing...If yes, connect to your instances and check thekubeletlogs for errors, they maybe are in trouble to register to your control plane.
– Eduardo Baitello
Mar 23 at 14:28
Do you mean has CloudFormation created the EC2 instances? I see the cluster in EKS dashboard but I don't see any EC2 instances associated with the cluster. I don't see any Events in CloudFormation > Stack > myStack > Events either. See the updated question for when I launch a cluster using the Kubernetes API from my backend. I imagine that the master should be visible always?
– kilgoretrout
Mar 25 at 18:33
EKS worker nodes run in your AWS account as standard EC2 instances and connect to your cluster's control plane via the API server endpoint. The control plane (i.e., the master components) runs in an account managed by AWS, and it's always "hidden" from your point of view. See Amazon EKS Clusters.
– Eduardo Baitello
Apr 18 at 1:59
add a comment |
I am trying to setup an AWS EKS cluster and followed the instructions in https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html. But while trying to setup the dashboard I realized I do not have any nodes and don't know why.
Yes, I made sure that the CloudFormation stack for my nodes has the exact name of my EKS cluster and I applied the aws-auth-cm.yaml with the stacks NodeInstanceRole.
A similar question came up here Amazon Kubernetes AWS-EKS is not getting created properly or not synched with kubectl but there is no usable information there.
Here is some info:
$ kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP <IP> <none> 443/TCP 11d
$ kubectl get all --namespace=default
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP <IP> <none> 443/TCP 11d
$ kubectl get nodes --namespace=kube-system
No resources found.
get nodes gives No resources found for any of the namespaces I have: kube-system, kube-public, or default.
$ kubectl get all --namespace=kube-system
NAME READY STATUS RESTARTS AGE
pod/heapster-7ff8d6bf9f-qv56t 0/1 Pending 0 44m
pod/kube-dns-69ff9fcd66-ls9w7 0/3 Pending 0 11d
pod/kubernetes-dashboard-669f9bbd46-xthpq 0/1 Pending 0 45m
pod/monitoring-influxdb-cc95575b9-qjk4r 0/1 Pending 0 44m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/heapster ClusterIP <IP> <none> 80/TCP 44m
service/kube-dns ClusterIP <IP> <none> 53/UDP,53/TCP 11d
service/kubernetes-dashboard ClusterIP <IP> <none> 443/TCP 45m
service/monitoring-influxdb ClusterIP <IP> <none> 8086/TCP 44m
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/aws-node 0 0 0 0 0 <none> 11d
daemonset.apps/kube-proxy 0 0 0 0 0 <none> 11d
daemonset.apps/nvidia-device-plugin-daemonset 0 0 0 0 0 <none> 34m
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
deployment.apps/heapster 1 1 1 0 44m
deployment.apps/kube-dns 1 1 1 0 11d
deployment.apps/kubernetes-dashboard 1 1 1 0 45m
deployment.apps/monitoring-influxdb 1 1 1 0 44m
NAME DESIRED CURRENT READY AGE
replicaset.apps/heapster-7ff8d6bf9f 1 1 0 44m
replicaset.apps/kube-dns-69ff9fcd66 1 1 0 11d
replicaset.apps/kubernetes-dashboard-669f9bbd46 1 1 0 45m
replicaset.apps/monitoring-influxdb-cc95575b9 1 1 0 44m
UPDATE:
After I send a Kubernetes API call from my backend to launch some pods I get the following output (kubectl get jobs is similar) but still no actual instances spin up and the jobs never execute.
$ kubectl get svc
kubernetes ClusterIP <IP> <none> 443/TCP 14d
svc-3d1de3dc-7ca1-1f83-7a5e-548e5c5b4d12 NodePort <IP> <none> 8082:32433/TCP,8081:30374/TCP,8096:31178/TCP,8083:31067/TCP 1m
svc-3d1de3dc-7ca1-1f83-7a5e-548e5c5b4d12-sut0 ClusterIP <IP> <none> 50001/TCP 1m
svc-7429ae6b-6f4b-012b-2d93-7c244109090b NodePort <IP> <none> 8082:30736/TCP,8081:31272/TCP,8096:30857/TCP,8083:30949/TCP 1m
svc-7429ae6b-6f4b-012b-2d93-7c244109090b-sut0 ClusterIP <IP> <none> 50001/TCP 1m
svc-89e81309-f6e4-21b1-ab8d-ecfb74d08010 NodePort <IP> <none> 8082:32072/TCP,8081:31236/TCP,8096:30000/TCP,8083:31257/TCP 1m
svc-89e81309-f6e4-21b1-ab8d-ecfb74d08010-sut0 ClusterIP <IP> <none> 50001/TCP 1m
svc-c196e61f-098e-7b10-9d05-6d06ccbdbb9f NodePort <IP> <none> 8082:32541/TCP,8081:30305/TCP,8096:31738/TCP,8083:31846/TCP 1m
svc-c196e61f-098e-7b10-9d05-6d06ccbdbb9f-sut0 ClusterIP <IP> <none> 50001/TCP 1m
amazon-web-services
kubernetes amazon-eks aws-eks asked Mar 22 at 23:56
kilgoretroutkilgoretrout
1,15421732
I am trying to setup an AWS EKS cluster and followed the instructions in https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html. But while trying to setup the dashboard I realized I do not have any nodes and don't know why.
Yes, I made sure that the CloudFormation stack for my nodes has the exact name of my EKS cluster and I applied the aws-auth-cm.yaml with the stacks NodeInstanceRole.
A similar question came up here Amazon Kubernetes AWS-EKS is not getting created properly or not synched with kubectl but there is no usable information there.
Here is some info:
$ kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP <IP> <none> 443/TCP 11d
$ kubectl get all --namespace=default
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP <IP> <none> 443/TCP 11d
$ kubectl get nodes --namespace=kube-system
No resources found.
get nodes gives No resources found for any of the namespaces I have: kube-system, kube-public, or default.
$ kubectl get all --namespace=kube-system
NAME READY STATUS RESTARTS AGE
pod/heapster-7ff8d6bf9f-qv56t 0/1 Pending 0 44m
pod/kube-dns-69ff9fcd66-ls9w7 0/3 Pending 0 11d
pod/kubernetes-dashboard-669f9bbd46-xthpq 0/1 Pending 0 45m
pod/monitoring-influxdb-cc95575b9-qjk4r 0/1 Pending 0 44m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/heapster ClusterIP <IP> <none> 80/TCP 44m
service/kube-dns ClusterIP <IP> <none> 53/UDP,53/TCP 11d
service/kubernetes-dashboard ClusterIP <IP> <none> 443/TCP 45m
service/monitoring-influxdb ClusterIP <IP> <none> 8086/TCP 44m
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/aws-node 0 0 0 0 0 <none> 11d
daemonset.apps/kube-proxy 0 0 0 0 0 <none> 11d
daemonset.apps/nvidia-device-plugin-daemonset 0 0 0 0 0 <none> 34m
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
deployment.apps/heapster 1 1 1 0 44m
deployment.apps/kube-dns 1 1 1 0 11d
deployment.apps/kubernetes-dashboard 1 1 1 0 45m
deployment.apps/monitoring-influxdb 1 1 1 0 44m
NAME DESIRED CURRENT READY AGE
replicaset.apps/heapster-7ff8d6bf9f 1 1 0 44m
replicaset.apps/kube-dns-69ff9fcd66 1 1 0 11d
replicaset.apps/kubernetes-dashboard-669f9bbd46 1 1 0 45m
replicaset.apps/monitoring-influxdb-cc95575b9 1 1 0 44m
UPDATE:
After I send a Kubernetes API call from my backend to launch some pods I get the following output (kubectl get jobs is similar) but still no actual instances spin up and the jobs never execute.
$ kubectl get svc
kubernetes ClusterIP <IP> <none> 443/TCP 14d
svc-3d1de3dc-7ca1-1f83-7a5e-548e5c5b4d12 NodePort <IP> <none> 8082:32433/TCP,8081:30374/TCP,8096:31178/TCP,8083:31067/TCP 1m
svc-3d1de3dc-7ca1-1f83-7a5e-548e5c5b4d12-sut0 ClusterIP <IP> <none> 50001/TCP 1m
svc-7429ae6b-6f4b-012b-2d93-7c244109090b NodePort <IP> <none> 8082:30736/TCP,8081:31272/TCP,8096:30857/TCP,8083:30949/TCP 1m
svc-7429ae6b-6f4b-012b-2d93-7c244109090b-sut0 ClusterIP <IP> <none> 50001/TCP 1m
svc-89e81309-f6e4-21b1-ab8d-ecfb74d08010 NodePort <IP> <none> 8082:32072/TCP,8081:31236/TCP,8096:30000/TCP,8083:31257/TCP 1m
svc-89e81309-f6e4-21b1-ab8d-ecfb74d08010-sut0 ClusterIP <IP> <none> 50001/TCP 1m
svc-c196e61f-098e-7b10-9d05-6d06ccbdbb9f NodePort <IP> <none> 8082:32541/TCP,8081:30305/TCP,8096:31738/TCP,8083:31846/TCP 1m
svc-c196e61f-098e-7b10-9d05-6d06ccbdbb9f-sut0 ClusterIP <IP> <none> 50001/TCP 1m
amazon-web-services
kubernetes amazon-eks aws-eks amazon-web-services
kubernetes amazon-eks aws-eks asked Mar 22 at 23:56
kilgoretroutkilgoretrout
1,15421732
asked Mar 22 at 23:56
kilgoretroutkilgoretrout
1,15421732
edited Mar 27 at 20:36
kilgoretrout
asked Mar 22 at 23:56
kilgoretroutkilgoretrout
1,15421732
asked Mar 22 at 23:56
kilgoretroutkilgoretrout
1,15421732
asked Mar 22 at 23:56
kilgoretroutkilgoretrout
1,15421732
1,15421732
2
Has CloudFormation created the ECS instances for your nodes? If no, they are missing...If yes, connect to your instances and check thekubeletlogs for errors, they maybe are in trouble to register to your control plane.
– Eduardo Baitello
Mar 23 at 14:28
Do you mean has CloudFormation created the EC2 instances? I see the cluster in EKS dashboard but I don't see any EC2 instances associated with the cluster. I don't see any Events in CloudFormation > Stack > myStack > Events either. See the updated question for when I launch a cluster using the Kubernetes API from my backend. I imagine that the master should be visible always?
– kilgoretrout
Mar 25 at 18:33
EKS worker nodes run in your AWS account as standard EC2 instances and connect to your cluster's control plane via the API server endpoint. The control plane (i.e., the master components) runs in an account managed by AWS, and it's always "hidden" from your point of view. See Amazon EKS Clusters.
– Eduardo Baitello
Apr 18 at 1:59
add a comment |
2
Has CloudFormation created the ECS instances for your nodes? If no, they are missing...If yes, connect to your instances and check thekubeletlogs for errors, they maybe are in trouble to register to your control plane.
– Eduardo Baitello
Mar 23 at 14:28
Do you mean has CloudFormation created the EC2 instances? I see the cluster in EKS dashboard but I don't see any EC2 instances associated with the cluster. I don't see any Events in CloudFormation > Stack > myStack > Events either. See the updated question for when I launch a cluster using the Kubernetes API from my backend. I imagine that the master should be visible always?
– kilgoretrout
Mar 25 at 18:33
EKS worker nodes run in your AWS account as standard EC2 instances and connect to your cluster's control plane via the API server endpoint. The control plane (i.e., the master components) runs in an account managed by AWS, and it's always "hidden" from your point of view. See Amazon EKS Clusters.
– Eduardo Baitello
Apr 18 at 1:59
2
2
Has CloudFormation created the ECS instances for your nodes? If no, they are missing...If yes, connect to your instances and check the
kubelet logs for errors, they maybe are in trouble to register to your control plane.– Eduardo Baitello
Mar 23 at 14:28
Has CloudFormation created the ECS instances for your nodes? If no, they are missing...If yes, connect to your instances and check the
kubelet logs for errors, they maybe are in trouble to register to your control plane.– Eduardo Baitello
Mar 23 at 14:28
Do you mean has CloudFormation created the EC2 instances? I see the cluster in EKS dashboard but I don't see any EC2 instances associated with the cluster. I don't see any Events in CloudFormation > Stack > myStack > Events either. See the updated question for when I launch a cluster using the Kubernetes API from my backend. I imagine that the master should be visible always?
– kilgoretrout
Mar 25 at 18:33
Do you mean has CloudFormation created the EC2 instances? I see the cluster in EKS dashboard but I don't see any EC2 instances associated with the cluster. I don't see any Events in CloudFormation > Stack > myStack > Events either. See the updated question for when I launch a cluster using the Kubernetes API from my backend. I imagine that the master should be visible always?
– kilgoretrout
Mar 25 at 18:33
EKS worker nodes run in your AWS account as standard EC2 instances and connect to your cluster's control plane via the API server endpoint. The control plane (i.e., the master components) runs in an account managed by AWS, and it's always "hidden" from your point of view. See Amazon EKS Clusters.
– Eduardo Baitello
Apr 18 at 1:59
EKS worker nodes run in your AWS account as standard EC2 instances and connect to your cluster's control plane via the API server endpoint. The control plane (i.e., the master components) runs in an account managed by AWS, and it's always "hidden" from your point of view. See Amazon EKS Clusters.
– Eduardo Baitello
Apr 18 at 1:59
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55309229%2fno-nodes-available-in-aws-eks%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55309229%2fno-nodes-available-in-aws-eks%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Has CloudFormation created the ECS instances for your nodes? If no, they are missing...If yes, connect to your instances and check the
kubeletlogs for errors, they maybe are in trouble to register to your control plane.– Eduardo Baitello
Mar 23 at 14:28
Do you mean has CloudFormation created the EC2 instances? I see the cluster in EKS dashboard but I don't see any EC2 instances associated with the cluster. I don't see any Events in CloudFormation > Stack > myStack > Events either. See the updated question for when I launch a cluster using the Kubernetes API from my backend. I imagine that the master should be visible always?
– kilgoretrout
Mar 25 at 18:33
EKS worker nodes run in your AWS account as standard EC2 instances and connect to your cluster's control plane via the API server endpoint. The control plane (i.e., the master components) runs in an account managed by AWS, and it's always "hidden" from your point of view. See Amazon EKS Clusters.
– Eduardo Baitello
Apr 18 at 1:59