IPv6 Support: Bootstrap process breaks when serviceIpv6Cidr isn't provided

[ravisinha0506]

What happened:
When service-ipv6-cidr isn't provided to bootstrap.sh script, it makes describe-cluster api to fetch this value and receives None. This is happening as awscli still points to an older version ( 1.18.X ) which doesn't return newly introduced parameters. As a result, None gets assigned toservice-ipv6-cidr.

What you expected to happen:
Bootstrap process should be able to fetch correct service-ipv6-cidr value from eks describe-cluster api.

How to reproduce it (as minimally and precisely as possible):
Use this userdata in IPv6 variant worker node:

MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="//"

--//
Content-Type: text/x-shellscript; charset="us-ascii"
#!/bin/bash
set -ex

/etc/eks/bootstrap.sh my-cluster --ip-family ipv6

--//--

[ravisinha0506]

As a workaround, all the params should be passed to the bootstrap script.

For ex:

MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="//"

--//
Content-Type: text/x-shellscript; charset="us-ascii"
#!/bin/bash
set -ex
B64_CLUSTER_CA=<CADATA>
API_SERVER_URL=<SOME_ENDPOINT>
SERVICE_IPV6_CIDR=<cidr>
/etc/eks/bootstrap.sh my-cluster --b64-cluster-ca $B64_CLUSTER_CA --apiserver-endpoint $API_SERVER_URL --ip-family ipv6 --service-ipv6-cidr  $SERVICE_IPV6_CIDR 

--//--

[ravisinha0506]

Latest AMI release has fix for this issue.

[ravisinha0506]

This issue would still appear for a custom AMI node group customer as default AWS CLI ( v1.18 ) wouldn't be able to fetch cluster information using eks:describeCluster api.

[archoversight]

#887

The assumption is that if you pass in the b64-cluster-ca and the apiserver-endpoint then it is IPv4...

[bryantbiggs]

I believe this is resolved with #860 - cc @bwagner5 / @suket22

[archoversight]

This issue likely won't be fixed with #860 either. This is related to the AWS CLI version being out of date. My comment above was that this is still broken if you pass just the b64 cluster ca and the apiserver endpoint, without providing the other IPv6 information.

[bwagner5]

AWS CLI has been updated, so this should be resolved now #1066