Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Empty output for get cluster #40

Closed
arun-gupta opened this issue Jun 6, 2018 · 2 comments · Fixed by #41
Closed

Empty output for get cluster #40

arun-gupta opened this issue Jun 6, 2018 · 2 comments · Fixed by #41

Comments

@arun-gupta
Copy link

Created a cluster:

2018-06-05T16:00:29-07:00 [ℹ]  importing SSH public key "/Users/argu/.ssh/id_rsa.pub" as "EKS-adorable-sculpture-1528239629"
2018-06-05T16:00:29-07:00 [ℹ]  creating EKS cluster "adorable-sculpture-1528239629"
2018-06-05T16:00:29-07:00 [ℹ]  creating VPC stack "EKS-adorable-sculpture-1528239629-VPC"
2018-06-05T16:00:29-07:00 [ℹ]  creating ServiceRole stack "EKS-adorable-sculpture-1528239629-ServiceRole"
2018-06-05T16:01:10-07:00 [✔]  created ServiceRole stack "EKS-adorable-sculpture-1528239629-ServiceRole"
2018-06-05T16:01:50-07:00 [✔]  created VPC stack "EKS-adorable-sculpture-1528239629-VPC"
2018-06-05T16:01:50-07:00 [ℹ]  creating control plane "adorable-sculpture-1528239629"
2018-06-05T16:10:32-07:00 [✔]  created control plane "adorable-sculpture-1528239629"
2018-06-05T16:10:32-07:00 [ℹ]  creating DefaultNodeGroup stack "EKS-adorable-sculpture-1528239629-DefaultNodeGroup"
2018-06-05T16:14:12-07:00 [✔]  created DefaultNodeGroup stack "EKS-adorable-sculpture-1528239629-DefaultNodeGroup"
2018-06-05T16:14:12-07:00 [✔]  all EKS cluster "adorable-sculpture-1528239629" resources has been created
2018-06-05T16:14:12-07:00 [ℹ]  wrote "kubeconfig"
2018-06-05T16:14:13-07:00 [ℹ]  the cluster has 0 nodes
2018-06-05T16:14:13-07:00 [ℹ]  waiting for at least 2 nodes to become ready
2018-06-05T16:14:59-07:00 [ℹ]  the cluster has 2 nodes
2018-06-05T16:14:59-07:00 [ℹ]  node "ip-192-168-236-174.us-west-2.compute.internal" is ready
2018-06-05T16:14:59-07:00 [ℹ]  node "ip-192-168-87-30.us-west-2.compute.internal" is ready
2018-06-05T16:14:59-07:00 [✖]  kubectl version v1.8.0 was found at "kubectl", minimum required version to use EKS is v1.10.0
2018-06-05T16:14:59-07:00 [ℹ]  cluster should be functions despite missing client binaries that need to be installed in the PATH

Upgraded kubectl to 1.10.2
Installed heptio-authenticator-aws in PATH
Had to grab cluster name from the log output
eksctl get cluster --cluster-name adorable-sculpture-1528239629 and eksctl get cluster --cluster-name adorable-sculpture-1528239629 --region us-west-2 is giving an empty output

@christopherhein
Copy link
Contributor

Thanks @arun-gupta glad to have you going through this as well. Looks like it a simple change the status key in the JSON response is looking for a Ready string when it should be ACTIVE per our docs. will have a PR in a second.

@christopherhein
Copy link
Contributor

Post this PR we'll need to make changes to make the output nicer see - #27

christopherhein added a commit that referenced this issue Jun 6, 2018
**Why:**

* This allows the logger to print out the status of all the
  Cloudformation Stacks use to create the cluster.

**This change addresses the need by:**

* closes #40

Signed-off-by: Christopher Hein <me@christopherhein.com>
torredil pushed a commit to torredil/eksctl that referenced this issue May 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants