Add an initial quick menu and update a couple of networking points

Signed-off-by: Manuel Buil <[email protected]>

docs/installation/network-options.md

@@ -3,7 +3,15 @@ title: "Network Options"
 weight: 25
 ---
 
-This page describes K3s network configuration options, including configuration or replacement of Flannel, and configuring IPv6.
+This page describes K3s network configuration options:
+
+- [Flannel options](#flannel-options)
+- [Custom CNI](#custom-cni)
+- [Control-Plane Egress Selector configuration](#control-plane-egress-selector-configuration)
+- [Dual-stack (IPv4 + IPv6) Networking](#dual-stack-ipv4--ipv6-networking)
+- [Single-stack IPv6 Networking](#single-stack-ipv6-networking)
+- [Distributed hybrid or multicloud cluster](#distributed-hybrid-or-multicloud-cluster)
+
 
 > **Note:** Please reference the [Networking](../networking/networking.md) page for information about CoreDNS, Traefik, and the Service LB.
 
@@ -141,7 +149,7 @@ Stable support is available as of [v1.23.7+k3s1](https://github.com/k3s-io/k3s/r
 
 :::caution Known Issue 
 
-Kubernetes [Issue #111695](https://github.com/kubernetes/kubernetes/issues/111695) causes the Kubelet to ignore the node IPv6 addresses if you have a dual-stack environment and you are not using the primary network interface for cluster traffic. To avoid this bug, add the following flag to both K3s servers and agents:
+Before 1.27, Kubernetes [Issue #111695](https://github.com/kubernetes/kubernetes/issues/111695) causes the Kubelet to ignore the node IPv6 addresses if you have a dual-stack environment and you are not using the primary network interface for cluster traffic. To avoid this bug, use 1.27 or newer or add the following flag to both K3s servers and agents:
 
 ```
 --kubelet-arg="node-ip=0.0.0.0" # To proritize IPv4 traffic
@@ -163,6 +171,10 @@ Note that you may configure any valid `cluster-cidr` and `service-cidr` values,
 
 If you are using a custom CNI plugin, i.e. a CNI plugin other than Flannel, the additional configuration may be required. Please consult your plugin's dual-stack documentation and verify if network policies can be enabled.
 
+:::caution Known Issue
+When defining cluster-cidr and service-cidr, if the first IPFamily is IPv6, node-ip should be specified if you want the main IP of the pods to be IPv6, otherwise kubelet will always pick IPv4.
+:::
+
 ## Single-stack IPv6 Networking
 
 :::info Version Gate