-
Notifications
You must be signed in to change notification settings - Fork 951
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
Wrong Internal-IP for Bottlerocket node in IPv6 kubernetes cluster #3623
Labels
question
Further information is requested
Comments
Could you share your AWSNodeTemplate as well? |
Of course, no problem. I put it into ticket.
…On Tue, Mar 21, 2023 at 6:14 PM Nick Tran ***@***.***> wrote:
Could you share your AWSNodeTemplate as well?
—
Reply to this email directly, view it on GitHub
<#3623 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKRYDMQC7C2ME67YOA5ZNXDW5HOYPANCNFSM6AAAAAAWCPNJFA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I just tested an IPv6 setup with Bottlerocket and it is registering with an IPv6 Internal IP. It looks like the version of Bottlerocket you're launching is a little older than mine. Can you try using Bottlerocket OS 1.13.1?
|
bwagner5
added
question
Further information is requested
and removed
bug
Something isn't working
labels
Apr 4, 2023
Hi everyone, |
nazarewk
added a commit
to nazarewk/terraform-aws-eks-blueprints
that referenced
this issue
Apr 24, 2023
fixes aws/karpenter-provider-aws#3623 OOTB issue for IPv6 clusters
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
Karpenter Version: v0.27.0
Kubernetes Version: v1.25.0
Expected Behavior
The newly provisioned node based on the Bottlerocket OS-Image should register in the IPv6 EKS kubernetes cluster with Internal-IP family IPv6 (like for Amazon Linux 2). Now, unfortunately, it gets IPv4 IP address.
Actual Behavior
The Bottlerocket node registers in IPv6 kubernetes cluster with IPv4 as Internal-IP
Steps to Reproduce the Problem
Karpenter deployed from chelm v0.27.0
The newest Kubernetes v1.25.0
Resource Specs and Logs
Community Note
The text was updated successfully, but these errors were encountered: