From 0059404cfddb86d19e40ebafba6e38c8934942c6 Mon Sep 17 00:00:00 2001 From: Benjamin Schimke Date: Thu, 16 Jan 2025 14:03:13 +0100 Subject: [PATCH] Clarify IPv6-only docs interface binding If a user want to run an IPv6-only cluster on a dualstack host, it will fail without specified the bind address because the snap will bind to the default (IPv4) interface that is available. Adding a note to make the user aware of this. --- docs/src/snap/howto/networking/ipv6.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/docs/src/snap/howto/networking/ipv6.md b/docs/src/snap/howto/networking/ipv6.md index 782ed0c0c..84b34565f 100644 --- a/docs/src/snap/howto/networking/ipv6.md +++ b/docs/src/snap/howto/networking/ipv6.md @@ -28,6 +28,13 @@ only IPv6 CIDRs are used. Start by bootstrapping the Kubernetes cluster and providing only IPv6 CIDRs for pods and services: +```{important} +To run an IPv6-only cluster on a host with both IPv4 and IPv6 interfaces, +you must include `--address ::/0` in the bootstrap and join commands. +Without this option, the snap will attempt to bind to the IPv4 interface, +which will fail if only IPv6 CIDRs are configured. +``` + ```bash sudo k8s bootstrap --timeout 10m --interactive ``` @@ -35,8 +42,8 @@ sudo k8s bootstrap --timeout 10m --interactive When prompted, set the pod and service CIDRs to IPv6 ranges. For example: ``` -Please set the Pod CIDR: [fd01::/108] -Please set the Service CIDR: [fd98::/108] +Please set the Pod CIDR: fd01::/108 +Please set the Service CIDR: fd98::/108 ``` Alternatively, these values can be configured in a bootstrap configuration file