Skip to content

Commit c7809f5

Browse files
committed
fix: md linting
Signed-off-by: Reza Abbasalipour <[email protected]>
1 parent 5746ed9 commit c7809f5

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

docs/canonicalk8s/snap/reference/upgrading.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,35 +3,47 @@
33
## Upgrade Instructions
44

55
### 1.32 -> 1.33
6+
67
Updating the {{product}} snap to version 1.33 is straightforward in most cases.
78
If you are not using dual stack networking, you can simply run:
89

910
```bash
1011
sudo snap refresh k8s --channel=1.33/stable
1112
```
13+
1214
All components, including Cilium, will be updated automatically.
1315

1416
#### Additional Steps for Dual Stack Environments
17+
1518
If your cluster is configured with dual stack networking (IPv4 and IPv6),
1619
you’ll need to make a manual adjustment before refreshing. {{product}} 1.33
1720
includes Cilium v1.17, which introduces a stricter requirement for dual stack:
1821
Each node must report both IPv4 and IPv6 addresses to the API server.
1922
If this is not satisfied, the Cilium agent pods will fail to start.
2023
For each node in the cluster, perform the following steps:
24+
2125
- Edit the kubelet configuration:
26+
2227
```bash
2328
sudo nano /var/snap/k8s/common/args/kubelet
2429
```
30+
2531
- Locate the --node-ip flag.
26-
- Add both the IPv4 and IPv6 addresses (comma-separated) from the same interface:
32+
- Add both the IPv4 and IPv6 addresses (comma-separated) from the same
33+
interface:
34+
2735
```bash
2836
--node-ip=<IPv4>,<IPv6>
2937
```
38+
3039
- Restart the `kubelet` service
40+
3141
```bash
3242
sudo systemctl restart snap.k8s.kubelet.service
3343
```
44+
3445
- Restart the Cilium DaemonSet:
46+
3547
```bash
3648
sudo k8s kubectl rollout restart daemonset cilium -n kube-system
3749
```

0 commit comments

Comments
 (0)