Eksctl: [0.1.20-rc.3] For 'get nodegroup' the 'CLUSTER' column is blank

[whereisaaron]

What happened?
The get nodegroup command produces an empty CLUSTER column.

What you expected to happen?
Expected the cluster name specified with the requires --cluster parameter to appear in that column

How to reproduce it?

$ bin/eksctl get nodegroup
[✖]  --cluster must be set
$ eksctl get nodegroup --cluster foo
CLUSTER NODEGROUP       CREATED                 MIN SIZE        MAX SIZE        DESIRED CAPACITY        INSTANCE TYPE   IMAGE ID
        group-1         2019-02-05T23:05:07Z    1               4               2                       m5.large        ami-0c2e8d28b1f854c68

Versions
Please paste in the output of these commands:

$ eksctl version
[ℹ]  version.Info{BuiltAt:"", GitCommit:"", GitTag:"0.1.20-rc.3"}
$ uname -a
Linux 4.4.0-17763-Microsoft #253-Microsoft Mon Dec 31 17:49:00 PST 2018 x86_64 x86_64 x86_64 GNU/Linux
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.4", GitCommit:"f49fa022dbe63faafd0da106ef7e05a29721d3f1", GitTreeState:"clean", BuildDate:"2018-12-14T07:10:00Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.5-eks-6bad6d", GitCommit:"6bad6d9c768dc0864dab48a11653aa53b5a47043", GitTreeState:"clean", BuildDate:"2018-12-06T23:13:14Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

Also include your version of heptio-authenticator-aws -> N/A

Logs

2019-02-05T19:09:34-05:00 [▶]  role ARN for the current session is "arn:aws:iam::123456789012:user/bar"
2019-02-05T19:09:34-05:00 [▶]  nodegroups = [{
  Capabilities: ["CAPABILITY_NAMED_IAM"],
  CreationTime: 2019-02-05 23:05:07.696 +0000 UTC,
  Description: "EKS nodes (AMI family: AmazonLinux2, SSH access: true, subnet topology: Private) [created and managed by eksctl]",
  DisableRollback: false,
  EnableTerminationProtection: false,
  Outputs: [
    {
      OutputKey: "FeaturePrivateNetworking",
      OutputValue: "true"
    },
    {
      ExportName: "eksctl-foo-nodegroup-group-1::InstanceRoleARN",
      OutputKey: "InstanceRoleARN",
      OutputValue: "arn:aws:iam::123456789012:role/eksctl-foo-nodegroup-group-1-NodeInstanceRole-83GQAA20GX8M"
    },
    {
      OutputKey: "FeatureLocalSecurityGroup",
      OutputValue: "true"
    },
    {
      ExportName: "eksctl-foo-nodegroup-group-1::InstanceProfileARN",
      OutputKey: "InstanceProfileARN",
      OutputValue: "arn:aws:iam::123456789012:instance-profile/eksctl-foo-nodegroup-group-1-NodeInstanceProfile-12MO0AAWUV9XJ"
    },
    {
      OutputKey: "FeatureSharedSecurityGroup",
      OutputValue: "true"
    }
  ],
  RollbackConfiguration: {

  },
  StackId: "arn:aws:cloudformation:us-east-2:123456789012:stack/eksctl-foo-nodegroup-group-1/7b00e770-299a-11e9-ab89-06413d85a3ea",
  StackName: "eksctl-foo-nodegroup-group-1",
  StackStatus: "CREATE_COMPLETE",
  Tags: [{
      Key: "eksctl.cluster.k8s.io/v1alpha1/cluster-name",
      Value: "foo"
    },{
      Key: "eksctl.io/v1alpha2/nodegroup-name",
      Value: "group-1"
    }]
}]
CLUSTER NODEGROUP       CREATED                 MIN SIZE        MAX SIZE        DESIRED CAPACITY        INSTANCE TYPE   IMAGE ID
        group-1         2019-02-05T23:05:07Z    1               4               2                       m5.large        ami-0c2e8d28b1f854c68

[mumoshu]

Thanks for reporting!
https://github.com/weaveworks/eksctl/commit/191bb1adb14b149060814cd94b9770dbca14fa3b#diff-2635db5cd7bb8d81775baf6fb2be0fdeR61 seems to have introduced the issue. I've submitted the fix #511.