add IPv6 to cluster-dns Usage Docs #11498
Open
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.
Proposed Changes
This update is based on the related PR/MR: rancher/rke2-docs#303.
While the RKE2/K3s clusterDNS variable (cluster-dns) supports both IPv4 and IPv6, the current documentation does not explicitly mention the option to use an IPv6 address for the cluster DNS. Users can configure the cluster DNS to use an IPv4, IPv6, or dual-stack address, as supported by the relevant script logic.
Types of Changes
Add explicit documentation for IPv6 support in the ClusterDNS usage section, highlighting its capability to handle IPv6 addresses.
Verification
The ClusterDNS can be configured to use IPv4/IPv6 addresses based on the CIDRs specified in config.yaml. By default, the IPv4 ClusterIP is 10.43.0.10. If an address from an IPv6 CIDR is specified, the ClusterDNS service will also receive an IPv6 address.
Testing
Ensure that IPv6 addresses are correctly assigned to the ClusterDNS service when an IPv6 CIDR is configured under
IPs:
when usingkubectl describe svc rke2-coredns-rke2-coredns
Linked Issues
This update is based on the related PR/MR: rancher/rke2-docs#303.
User-Facing Change
Further Comments