siderolabs / siderolabs/docs

Document ipv4/ipv6 dualstack settings

Open
#88 0 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted need infrastructure
Dominant language
MDX
Stars
11
Forks
76
Avg merge
3d 5h
Merged PRs (30d)
26

Description

Bug Report

Description

Dualstack seems to work according to https://github.com/siderolabs/talos/issues/8115#issue-2056553134.
But I still couldn't find any documentation about this - apart from some github issues around the topic.
It feels clunky & definitely not like it's a supported configuration.
If you add ipv6 - even if it's just as dualstack setup - to your docs, it'd definitely be a statement that it's a supported feature and you have it in mind for future development.

Some ideas for the docs

Some cases you could include:

Dualstack for nodes & controlplane

This comes from reading the k8s & kubeadm dualstack docs and aims at specifying dualstack node-ips either statically or via DHCP/DHCPv6.

As an improvement example, why is there no machine.network.ipv6: true which also automatically enables DHCPv6?
From what I read, I need to go via machine.network.interfaces[...].dhcpOptions.ipv6. What if I - similarly to the ipv4 setup - don't care about the interface-naming, and just want to enable ipv6?

Or, it feels weird to set node-specific kubelet flags like podCIDR (I think that relates to cluster.network.podSubnets) in the cluster settings of the machineconfig. From my understanding so far, it's more or less expected that the cluster-config is the same on all talos nodes, but the podCIDR can be host-specific... So it'd be nice if there's a more concise documentation on this.

Dualstack with flannel

For a simple example dualstack CNI setup with podCIDR & serviceCIDR.

Dualstack for podCIDR and serviceCIDR with cilium

For cluster-internal networking with podCIDR & serviceCIDR with a more complex CNI.
Since you have explicit cilium docs for other topics, I figure this makes sense as well.

Special case:
In the Cilium kubernetes-ipam docs, I read that the (ipv6) podCIDRs can automatically be set by the hostCIDR - so there's no need for NATing. That sounds too good to be true lol.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Kubernetes dual-stack and kubeadm documentation, then identify the corresponding Talos machine configuration settings. Cover dual-stack nodes and control planes, Flannel, and Cilium pod and service CIDRs, with examples for the requested cases. Done means the documentation clearly explains supported IPv4/IPv6 settings and configuration paths.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
documentation, networking
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.