You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|[calico](katalog/calico)|`3.26.3`|[Calico][calico-page] CNI Plugin. For cluster with `< 50` nodes. |
33
-
|[cilium](katalog/cilium)|`1.14.3`|[Cilium][cilium-page] CNI Plugin. For cluster with `< 200` nodes. |
34
-
|[tigera](katalog/tigera)|`1.30.7`|[Tigera Operator][tigera-page], a Kubernetes Operator for Calico, provides pre-configured installations for on-prem and for EKS in policy-only mode. |
32
+
|[calico](katalog/calico)|`3.27.0`|[Calico][calico-page] CNI Plugin. For cluster with `< 50` nodes. |
33
+
|[cilium](katalog/cilium)|`1.15.2`|[Cilium][cilium-page] CNI Plugin. For cluster with `< 200` nodes. |
34
+
|[tigera](katalog/tigera)|`1.32.3`|[Tigera Operator][tigera-page], a Kubernetes Operator for Calico, provides pre-configured installations for on-prem and for EKS in policy-only mode. |
35
35
|[ip-masq](katalog/ip-masq)|`2.8.0`| The `ip-masq-agent` configures iptables rules to implement IP masquerading functionality |
36
36
37
37
> The resources in these packages are going to be deployed in `kube-system` namespace. Except for the operator.
@@ -42,9 +42,9 @@ Click on each package to see its full documentation.
Welcome to the latest release of the `Networking` module of [`Kubernetes Fury Distribution`](https://github.com/sighupio/fury-distribution) maintained by team SIGHUP.
4
+
5
+
This minor release updates some components and adds support to Kubernetes 1.28.
6
+
7
+
## Component Images 🚢
8
+
9
+
| Component | Supported Version | Previous Version |
2. Ensure that the number of READY pods is the same number of Cilium pods running.
43
+
```text
44
+
kubectl get daemonset -n kube-system | sed -n '1p;/cilium/p'
45
+
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
46
+
cilium 2 2 2 2 2 <none> 1h20m
47
+
cilium-pre-flight-check 2 2 2 2 2 <none> 7m15s
48
+
```
49
+
50
+
3. Once the number of READY pods is equal, make sure the Cilium pre-flight deployment is also marked as READY 1/1.
51
+
If it shows READY 0/1, consult the [CNP Validation](https://docs.cilium.io/en/stable/operations/upgrade/#cnp-validation) section in the official docs and resolve issues with the deployment before continuing with the upgrade.
52
+
```text
53
+
kubectl get deployment -n kube-system cilium-pre-flight-check -w
54
+
NAME READY UP-TO-DATE AVAILABLE AGE
55
+
cilium-pre-flight-check 1/1 1 0 12s
56
+
```
57
+
58
+
4. Once the number of READY for the preflight DaemonSet is the same as the number of cilium pods running and the preflight Deployment is marked as READY 1/1 you can delete the cilium-preflight and proceed with the upgrade.
59
+
```bash
60
+
kubectl delete -f cilium-preflight.yaml
61
+
```
62
+
63
+
64
+
If you are upgrading from previous versions, please refer to the [`v1.15.0` release notes](https://github.com/sighupio/fury-kubernetes-networking/releases/tag/v1.15.0).
0 commit comments