Eksctl: 1.14 is not known in this version of eksctl

[ejsmith]

What happened?
Upgraded control plane to 1.14 using eksctl update cluster --name ats-auto --approve but then tried to use a config file to update the node groups and got an error saying 1.14 is not known in this version of eksctl.

$ eksctl version
[ℹ]  version.Info{BuiltAt:"", GitCommit:"", GitTag:"0.5.2"}

ejsmith at ejsmith in ~/infrastructure (master●)
$ eksctl update cluster -f eks-cluster.yaml
[ℹ]  using region us-east-1
[!]  NOTE: config file is used for finding cluster name and region
[!]  NOTE: cluster VPC (subnets, routing & NAT Gateway) configuration changes are not yet implemented
[✖]  control plane version "1.14" is not known to this version of eksctl, try to upgrade eksctl first

[cPu1]

Thanks for reporting this @ejsmith . The fix has been merged with master and would be available in the next release.

[thiagonache]

@ejsmith I've updated to 0.5.2 and could deploy 1.14 version. Seems to be working fine.

[sstkwayne]

I am still seeing this issue in v0.5.3

```
$ eksctl version
[ℹ] version.Info{BuiltAt:"", GitCommit:"", GitTag:"0.5.3"}

$ eksctl update cluster -f clusters/cluster.yaml --approve
[ℹ] using region us-east-1
[!] NOTE: config file is used for finding cluster name and region
[!] NOTE: cluster VPC (subnets, routing & NAT Gateway) configuration changes are not yet implemented
[✖] control plane version "1.14" is not known to this version of eksctl, try to upgrade eksctl first```

[girikuncoro]

same for me, I was able to update from 1.13 to 1.14 through eksctl, my current cluster is at 1.14

$ eksctl get cluster eks-test
NAME        VERSION STATUS ...
eks-test    1.14    ACTIVE  ...

but once I execute eksctl update again to update other config, I'm seeing the same issue

$ eksctl version
[ℹ]  version.Info{BuiltAt:"", GitCommit:"", GitTag:"0.5.3"}

$ eksctl update cluster -f eks-test.yaml
[ℹ]  using region ap-southeast-1
[!]  NOTE: config file is used for finding cluster name and region
[!]  NOTE: cluster VPC (subnets, routing & NAT Gateway) configuration changes are not yet implemented
[✖]  control plane version "1.14" is not known to this version of eksctl, try to upgrade eksctl first

[cPu1]

The fix is in master but we missed cherry-picking it for the 0.5.2 release. We'll include this fix in the next release.

[errordeveloper]

@cPu1 thanks for confirming this. I think 0.6.0 is close enough now. In my mind this bug is relatively low-priority, as it only affects clusters that are already on version 1.14. Unless anything else comes up, we shouldn't need another patch release and hold this for 0.6.0. I think it's okay to close the issue.

[sstkwayne]

@errordeveloper because of this bug I am unable to add/remove node groups for my 1.14 cluster so I think the priority on this bug should be a bit higher.

[thiagonache]

Use 0.5.2. It should fix your problem.

On Wed, Sep 11, 2019 at 11:41 AM Wayne Folkes [e-mail]
wrote:

@errordeveloper https://github.com/errordeveloper because of this bug I
am unable to add/remove node groups for my 1.14 cluster so I think the
priority on this bug should be a bit higher.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/weaveworks/eksctl/issues/1304?email_source=notifications&email_token=AATHKBKRLTV26U52LVKMH3TQJD7RRA5CNFSM4IUJO7LKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6OXGWQ#issuecomment-530412378,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AATHKBII2OJUBDETP4QFUQDQJD7RRANCNFSM4IUJO7LA
.

--

[]s

Thiago Nache

[thiagonache]

@errordeveloper are you sure the check picky was missed on 0.5.2 and not 0.5.3? because 0.5.2 works and 0.5.3 does not work

[sstkwayne]

@thiagonache it does not fix my problem. I pulled down 0.5.2 and I am getting the same error as I was getting with 0.5.3

$ ~/Downloads/eksctl version
[ℹ]  version.Info{BuiltAt:"", GitCommit:"", GitTag:"0.5.2"}
$ ~/Downloads/eksctl update cluster -f clusters/dev-us-east-1-general.yaml --approve
[ℹ]  using region us-east-1
[!]  NOTE: config file is used for finding cluster name and region
[!]  NOTE: cluster VPC (subnets, routing & NAT Gateway) configuration changes are not yet implemented
[✖]  control plane version "1.14" is not known to this version of eksctl, try to upgrade eksctl first

$ eksctl version
[ℹ]  version.Info{BuiltAt:"", GitCommit:"", GitTag:"0.5.3"}
$ eksctl update cluster -f clusters/dev-us-east-1-general.yaml --approve
[ℹ]  using region us-east-1
[!]  NOTE: config file is used for finding cluster name and region
[!]  NOTE: cluster VPC (subnets, routing & NAT Gateway) configuration changes are not yet implemented
[✖]  control plane version "1.14" is not known to this version of eksctl, try to upgrade eksctl first

[thiagonache]

@sstkwayne that's pretty odd

Thiagos-Mac-mini-02:bootstrap tnache$ eksctl version && grep 1.14 example.yaml && eksctl create cluster -f example.yaml 
[ℹ]  version.Info{BuiltAt:"", GitCommit:"", GitTag:"0.5.2"}
  version: "1.14"
[ℹ]  using region us-east-1
[ℹ]  setting availability zones to [us-east-1b us-east-1e]
[ℹ]  subnets for us-east-1b - public:192.168.0.0/19 private:192.168.64.0/19
[ℹ]  subnets for us-east-1e - public:192.168.32.0/19 private:192.168.96.0/19
[ℹ]  nodegroup "XXXXXXXX" will use "ami-03e43ca3afc5d79a3" [AmazonLinux2/1.14]
[ℹ]  using Kubernetes version 1.14
[ℹ]  creating EKS cluster "XXXXX-prod" in "us-east-1" region
[ℹ]  1 nodegroup (XXXXXX) was included (based on the include/exclude rules)
[ℹ]  will create a CloudFormation stack for cluster itself and 1 nodegroup stack(s)
[ℹ]  if you encounter any issues, check CloudFormation console or try 'eksctl utils describe-stacks --region=us-east-1 --name=XXXXX'
[ℹ]  3 sequential tasks: { create cluster control plane "XXXX", create nodegroup "XXXXX", update CloudWatch logging configuration }
[ℹ]  building cluster stack "XXXXX"
[ℹ]  deploying stack "XXXXXX"

What's the OS you are using? Did you build your own binary or downloaded it from https://github.com/weaveworks/eksctl/releases/tag/0.5.2?

[sstkwayne]

@thiagonache I am running MacOS 10.14.6 and yes I downloaded the binary from the releases page.

[cPu1]

@thiagonache this isn't an OS-related issue. This bug only affects eksctl update cluster, which is what @sstkwayne is trying. eksctl create cluster, which is what you've shown to work, is unaffected.

[thiagonache]

@cPu1 ah... my bad... I missed that.

[GergelyKalmar]

Is there going to be a fix for this soon? I cannot seem to be able to update our cluster/node group configuration at all due to this bug at the moment.

Also, the latest version of eksctl updated the control plane to 1.14, even though it was specified to be 1.13 in the cluster config file. So, I basically ended up with a production system that I can't manage now due to this... I tried all eksctl versions from 0.5.1 upwards and none work.

[GergelyKalmar]

In case anyone else is looking for a workaround: for now you can compile your own eksctl binary based on the current version of the master branch, that seems to be working.

[JWimsingues]

Hi there, I am running the same issue at the moment.

@GergelyKalmar when I tried to build the binary as you suggested (had the same idea in fact when reading the different stuff here and there) and I have another problem, linked with go. Here is my error:
make build go: github.com/goreleaser/[email protected] requires [email protected] requires contrib.go.opencensus.io/exporter/[email protected] requires github.com/census-instrumentation/[email protected]: invalid pseudo-version: version before v0.1.0 would have negative patch number go: github.com/goreleaser/[email protected] requires [email protected] requires contrib.go.opencensus.io/exporter/[email protected] requires github.com/census-instrumentation/[email protected]: invalid pseudo-version: version before v0.1.0 would have negative patch number go: github.com/goreleaser/[email protected] requires [email protected] requires contrib.go.opencensus.io/exporter/[email protected] requires github.com/census-instrumentation/[email protected]: invalid pseudo-version: version before v0.1.0 would have negative patch number env GOBIN=/Users/jwimsingues/go-workspace/bin/ time go generate ./pkg/nodebootstrap go: github.com/goreleaser/[email protected] requires [email protected] requires contrib.go.opencensus.io/exporter/[email protected] requires github.com/census-instrumentation/[email protected]: invalid pseudo-version: version before v0.1.0 would have negative patch number 0.26 real 0.18 user 0.11 sys make: *** [pkg/nodebootstrap/maxpods.go] Error 1

I comment here as I think a clear workaround might be useful to every one consulting this post. Let me know if you want me to remove/edit this message.

Edit: code format

[GergelyKalmar]

I did not see this issue when using the latest golang version (1.13). You need to first run make install-build-deps and then make build, that seemed to work for me on Ubuntu 16.04 LTS. You just need to be very patient, because there's _a lot_ of packages to be installed.

[shardulsrivastava]

@GergelyKalmar that worked thanks a lot..

[ejsmith]

This is still an issue. I can create a 1.14 cluster, but after that I can't update it.

[shardulsrivastava]

@ejsmith if you are stuck then you can build it in your local as mentioned here:
https://github.com/weaveworks/eksctl/issues/1304#issuecomment-532082546

[JWimsingues]

@GergelyKalmar It did the trick, thanks :-)

[cPu1]

The fix has been released in version 0.6.0: https://github.com/weaveworks/eksctl/releases/tag/0.6.0

[emilbader]

You are a hero!