Add support to run eksctl in an IPv6-only environment

[clyang82]

What happened?
A description of actual behavior (with error messages).

My environment is IPv6 enabled.

sh-4.4$ cat /proc/net/if_inet6
fe800000000000008cf3abfffe7af92c 03 40 20 80     eth0
00000000000000000000000000000001 01 80 10 80       lo
fd01000000000004707ad2fffe0000d7 03 40 00 80     eth0

the api endpoint is resolved as IPv4 address.

sh-4.4$ eksctl get cluster
[!]  retryable error (RequestError: send request failed
caused by: Get http://169.254.169.254/latest/meta-data/iam/security-credentials/: dial tcp 169.254.169.254:80: connect: network is unreachable) from ec2metadata/GetMetadata - will retry after delay of 53ms
[!]  retryable error (RequestError: send request failed
caused by: Get http://169.254.169.254/latest/meta-data/iam/security-credentials/: dial tcp 169.254.169.254:80: connect: network is unreachable) from ec2metadata/GetMetadata - will retry after delay of 106ms
[!]  retryable error (RequestError: send request failed
caused by: Get http://169.254.169.254/latest/meta-data/iam/security-credentials/: dial tcp 169.254.169.254:80: connect: network is unreachable) from ec2metadata/GetMetadata - will retry after delay of 180ms
[!]  retryable error (RequestError: send request failed
caused by: Get http://169.254.169.254/latest/meta-data/iam/security-credentials/: dial tcp 169.254.169.254:80: connect: network is unreachable) from ec2metadata/GetMetadata - will retry after delay of 296ms
[!]  retryable error (RequestError: send request failed
caused by: Get http://169.254.169.254/latest/meta-data/iam/security-credentials/: dial tcp 169.254.169.254:80: connect: network is unreachable) from ec2metadata/GetMetadata - will retry after delay of 688ms
[!]  retryable error (RequestError: send request failed
caused by: Get http://169.254.169.254/latest/meta-data/iam/security-credentials/: dial tcp 169.254.169.254:80: connect: network is unreachable) from ec2metadata/GetMetadata - will retry after delay of 1.472s

What you expected to happen?
eksctl can be run successfully in IPv6 environment.

[clyang82]

@errordeveloper @cPu1 @martina-if Could you please provide your comments here? Thanks.

[martina-if]

Hi @clyang82, can you please run the command in debug mode?

eksctl get cluster -v 4

I have never tried running eksctl from a local ipv6 environment. I suspect this is not supported at the moment.

[clyang82]

Thanks @martina-if for your response.

bash-5.0# ./eksctl get cluster -v 4
2020-02-27T03:55:25Z [▶]  no region specified in flags or config, setting to us-west-2
2020-02-27T03:55:25Z [!]  retryable error (RequestError: send request failed
caused by: Put http://169.254.169.254/latest/api/token: dial tcp 169.254.169.254:80: connect: network is unreachable) from ec2metadata/GetToken - will retry after delay of 32.311436ms
2020-02-27T03:55:25Z [!]  retryable error (RequestError: send request failed
caused by: Put http://169.254.169.254/latest/api/token: dial tcp 169.254.169.254:80: connect: network is unreachable) from ec2metadata/GetToken - will retry after delay of 80.356392ms
2020-02-27T03:55:25Z [!]  retryable error (RequestError: send request failed
caused by: Put http://169.254.169.254/latest/api/token: dial tcp 169.254.169.254:80: connect: network is unreachable) from ec2metadata/GetToken - will retry after delay of 188.934ms
2020-02-27T03:55:25Z [!]  retryable error (RequestError: send request failed
caused by: Put http://169.254.169.254/latest/api/token: dial tcp 169.254.169.254:80: connect: network is unreachable) from ec2metadata/GetToken - will retry after delay of 461.737528ms
2020-02-27T03:55:26Z [!]  retryable error (RequestError: send request failed
caused by: Put http://169.254.169.254/latest/api/token: dial tcp 169.254.169.254:80: connect: network is unreachable) from ec2metadata/GetToken - will retry after delay of 592.648976ms
2020-02-27T03:55:26Z [!]  retryable error (RequestError: send request failed
caused by: Put http://169.254.169.254/latest/api/token: dial tcp 169.254.169.254:80: connect: network is unreachable) from ec2metadata/GetToken - will retry after delay of 1.404667776s
2020-02-27T03:55:28Z [!]  retryable error (RequestError: send request failed
caused by: Put http://169.254.169.254/latest/api/token: dial tcp 169.254.169.254:80: connect: network is unreachable) from ec2metadata/GetToken - will retry after delay of 3.734132992s

bash-5.0# ./eksctl get cluster -v 6
2020-02-27T03:55:44Z [▶]  no region specified in flags or config, setting to us-west-2
2020-02-27T03:55:44Z [▶]  DEBUG: Request ec2metadata/GetToken Details:
---[ REQUEST POST-SIGN ]-----------------------------
PUT /latest/api/token HTTP/1.1
Host: 169.254.169.254
User-Agent: aws-sdk-go/1.26.4 (go1.13.4; linux; amd64)
Content-Length: 0
X-Aws-Ec2-Metadata-Token-Ttl-Seconds: 21600
Accept-Encoding: gzip


-----------------------------------------------------
2020-02-27T03:55:44Z [▶]  DEBUG: Send Request ec2metadata/GetToken failed, attempt 0/13, error RequestError: send request failed
caused by: Put http://169.254.169.254/latest/api/token: dial tcp 169.254.169.254:80: connect: network is unreachable
2020-02-27T03:55:44Z [!]  retryable error (RequestError: send request failed
caused by: Put http://169.254.169.254/latest/api/token: dial tcp 169.254.169.254:80: connect: network is unreachable) from ec2metadata/GetToken - will retry after delay of 47.019693ms
2020-02-27T03:55:44Z [▶]  DEBUG: Retrying Request ec2metadata/GetToken, attempt 1
2020-02-27T03:55:44Z [▶]  DEBUG: Request ec2metadata/GetToken Details:

Do you have plan to support IPv6 for eksctl ?

[martina-if]

Hi @clyang82 Thanks for the new logs.

Have you tried running the aws-cli in this environment? Does it work well?

Do you have plan to support IPv6 for eksctl ?

It's not in our near term plans, but let's make this issue a feature request and see if more users vote for it. Based on that we can prioritize it earlier.

[clyang82]

Thanks. aws cli does not work as well.

bash-5.0# aws version
Error relocating /usr/local/bin/aws: __strcat_chk: symbol not found
Error relocating /usr/local/bin/aws: __snprintf_chk: symbol not found
Error relocating /usr/local/bin/aws: __vfprintf_chk: symbol not found
Error relocating /usr/local/bin/aws: __strdup: symbol not found
Error relocating /usr/local/bin/aws: __stpcpy_chk: symbol not found
Error relocating /usr/local/bin/aws: __vsnprintf_chk: symbol not found
Error relocating /usr/local/bin/aws: __strncpy_chk: symbol not found
Error relocating /usr/local/bin/aws: __strcpy_chk: symbol not found
Error relocating /usr/local/bin/aws: __fprintf_chk: symbol not found
Error relocating /usr/local/bin/aws: __strncat_chk: symbol not found

[martina-if]

@clyang82 These messages look more like an installation issue than a problem specific to an IPv6 environment :/ I would try reinstalling it

[michaelbeaumont]

@clyang82 Can you clarify whether you're looking for ipv6-only support or exactly what kind of environment you have? I'm running eksctl in an IPv6-enabled environment without issue.

[clyang82]

Yes. I am looking for ipv6-only.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.