Skip to content
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

[Support for IPv6]: Steps to add k3d cluster with ipv6 Only #833

Open
Imboncy opened this issue Nov 2, 2021 · 7 comments
Open

[Support for IPv6]: Steps to add k3d cluster with ipv6 Only #833

Imboncy opened this issue Nov 2, 2021 · 7 comments
Assignees
Labels
enhancement New feature or request k3s This is likely an issue with k3s not k3d itself
Milestone

Comments

@Imboncy
Copy link

Imboncy commented Nov 2, 2021

Details

  • I want to run the k3d cluster with only Ipv6 enable but I could not find any informative docs. Can someone help me on that?

  • I have the Calico config that allows only ipv6 but when i launch the cluster it starts with IPv4 y default.

@Imboncy Imboncy added the enhancement New feature or request label Nov 2, 2021
@iwilltry42 iwilltry42 self-assigned this Nov 16, 2021
@iwilltry42 iwilltry42 added the k3s This is likely an issue with k3s not k3d itself label Nov 16, 2021
@iwilltry42 iwilltry42 added this to the Backlog milestone Nov 16, 2021
@iwilltry42
Copy link
Member

Hi @Imboncy , thanks for opening this issue!
Does the whole cluster (i.e. also the nodes) have to run in ipv6 only mode? (that's the only part that would affect k3d)
Anyway, it's not supported by upstream K3s yet (see k3s-io/k3s#284 & k3s-io/k3s#2123).

@olix0r
Copy link
Contributor

olix0r commented May 16, 2022

It looks like k3s-io/k3s#284 & k3s-io/k3s#2123 are resolved now.

@iwilltry42 If I understand correctly, it should now be possible to configure k3s to use an IPv6 pod network in k3d?

@iwilltry42
Copy link
Member

@olix0r didn't look into it again yet, but it's back on the list.
What about my question above?

Does the whole cluster (i.e. also the nodes) have to run in ipv6 only mode? (that's the only part that would affect k3d)

@iwilltry42 iwilltry42 modified the milestones: v5.5.0, v6.0.0 Jun 4, 2022
@olix0r
Copy link
Contributor

olix0r commented Jun 15, 2022

Does the whole cluster (i.e. also the nodes) have to run in ipv6 only mode? (that's the only part that would affect k3d).

I don't think this is required for my use case, though it would ultimately be a nice addition at some point.

Basically, we're hearing about more users of IPv6 clusters and want to use k3d as an integration testing environment (for Linkerd). We primarily care about pod-to-pod and pod-to-service communication for these tests.

@zalegrala
Copy link

I'm using k3d for a local development environment, and we've got a user who wants to deploy our stuff in an ipv6-only cluster. In order to test locally and ensure functionality, having k3d support an IPv6 only mode would be pretty handy for this use case.

@almereyda
Copy link

Implementing this support could start with support for the kubeAPI.hostIP key allowing IPv6 addresses, such as ::1:

$ K3D_FIX_CGROUPV2=true k3d cluster create --config k3d-config.yaml
FATA[0000] Schema Validation failed for config file k3d-config.yaml: - kubeAPI.hostIP: Does not match format 'ipv4'

@alpeb
Copy link

alpeb commented Feb 15, 2024

Hi @iwilltry42, any updates on this? We're finally adding IPv6 support for linkerd and would love to be able to have this tested via our current k3d-based integration tests suite.

@iwilltry42 iwilltry42 modified the milestones: v6.0.0, v5.7.0 Feb 15, 2024
@iwilltry42 iwilltry42 moved this from To do to In progress in Networking Feb 15, 2024
@iwilltry42 iwilltry42 modified the milestones: v5.7.0, v5.8.0 Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request k3s This is likely an issue with k3s not k3d itself
Projects
Status: In progress
Development

No branches or pull requests

6 participants