Fix AWS IMDS discovery of ipv6 and ipv4 addresses #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Testing in kubernetes/kops#16722 revealed we were returning an error when ipv6 wasn't found, instead of falling back to ipv4
https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/kops/16722/pull-kops-e2e-k8s-aws-calico/1819545673658273792/artifacts/13.52.61.91/etcd.log
error querying ec2 metadata service (for ipv6): operation error ec2imds: GetMetadata, http response error StatusCode: 404, request to EC2 IMDS failed
/cc @hakman