-
Notifications
You must be signed in to change notification settings - Fork 522
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kubelet, pluto: support IPv6 #1710
Conversation
e6cd791
to
88e2b6a
Compare
Push above addresses @webern 's comments.
|
This comment has been minimized.
This comment has been minimized.
Push above changes the approach to determining EKS cluster IP family. Instead of making a call to EKS API to determine the cluster's IP family, we check When users want to give their nodes an IPv6 node IP address for an IPv6 EKS Cluster, they need to set the cluster's DNS IP to This is a temporary measure until the EKS API provides ways to let us automatically determine the IP family and service IPv6 CIDR. |
Push above fixes README documentation for |
This adds a patch to the in-tree AWS cloud provider code to make kubelet append IPv6 addresses to the list of NodeAddresses.
Push above adds the patch to kubelet for supporting ipv6 node addresses in AWS. |
e3d6948
to
2e0ed0b
Compare
Pushes above addresses @bcressey 's comments. Tested the changes and they still work as expected. |
sources/api/pluto/src/main.rs
Outdated
))] | ||
AwsInfo { source: api::Error }, | ||
|
||
#[snafu(display("Missing field '{}' in EKS kubernetes network config response", field))] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit:
#[snafu(display("Missing field '{}' in EKS kubernetes network config response", field))] | |
#[snafu(display("Missing field '{}' in EKS network config response", field))] |
Push above addresses comments by @bcressey . Tested and things still work as expected. |
Push above addresses Matt's comment #1710 (comment) |
This adds support for retrieving IPv6 node IP address for IPv6 EKS clusters
Push above fixes the fallthrough for determining the cluster dns ip. |
Ran conformance tests with an IPv6 cluster and all tests passed. |
Issue number:
Closes #1696
Description of changes:
The testing below has been done with IPv6 changes in aws-vpc-cni that has yet to be formally released: aws/amazon-vpc-cni-k8s#1587
Testing done:
Testing for IPv6 EKS Clusters:
Created an AMI off of the built images and launched an EC2 instance in my IPv6 EKS cluster.
The node is able to get an IPv6 internal IP address:
Can run pods without problem. The pods get IPv6 addresses assigned without problem. I can ping external ipv4 and ipv6 addresses without problem.
Testing for IPv4 EKS Clusters:
Launched node with AMI in IPv4 cluster.
Node becomes Ready with the correct
node-ip
andcluster-dns-ip
:Can run pods without problem.
Ran conformance tests with an IPv6 cluster and all tests passed.
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.