Releases: sighupio/fury-kubernetes-networking
Release v1.17.0
Networking Core Module Release 1.17.0
Welcome to the latest release of the Networking module of Kubernetes Fury Distribution maintained by team SIGHUP.
This patch release updates some components and adds support to Kubernetes 1.29.
Component Images 🚢
| Component | Supported Version | Previous Version |
|---|---|---|
calico |
v3.27.3 |
v3.27.0 |
cilium |
v1.15.2 |
No update |
ip-masq |
v2.8.0 |
No update |
tigera-operator |
v1.32.7 |
v1.32.3 |
Please refer the individual release notes to get detailed information on each release.
Update Guide 🦮
Process
- Just deploy as usual:
kustomize build katalog/calico | kubectl apply -f -
# OR
kustomize build katalog/tigera/on-prem | kubectl apply -f -
# OR
kustomize build katalog/cilium | kubectl apply -f -If you are upgrading from previous versions, please refer to the v1.16.0 release notes.
Preview v1.16.1-rc.3
63c808e
nutellinoit
Samuele Chiocca
Networking Core Module Release 1.16.1
Welcome to the latest release of the Networking module of Kubernetes Fury Distribution maintained by team SIGHUP.
This minor release updates some components and adds support to Kubernetes 1.29.
Component Images 🚢
| Component | Supported Version | Previous Version |
|---|---|---|
calico |
v3.27.3 |
v3.27.0 |
cilium |
v1.15.2 |
No update |
ip-masq |
v2.8.0 |
No update |
tigera-operator |
v1.32.7 |
v1.32.3 |
Please refer the individual release notes to get detailed information on each release.
Update Guide 🦮
Process
- Just deploy as usual:
kustomize build katalog/calico | kubectl apply -f -
# OR
kustomize build katalog/tigera/on-prem | kubectl apply -f -
# OR
kustomize build katalog/cilium | kubectl apply -f -If you are upgrading from previous versions, please refer to the v1.16.0 release notes.
Release v1.16.0
Networking Core Module Release 1.16.0
Welcome to the latest release of the Networking module of Kubernetes Fury Distribution maintained by team SIGHUP.
This minor release updates some components and adds support to Kubernetes 1.28.
Component Images 🚢
| Component | Supported Version | Previous Version |
|---|---|---|
calico |
v3.27.0 |
v3.26.3 |
cilium |
v1.15.2 |
v1.14.3 |
ip-masq |
v2.8.0 |
No update |
tigera-operator |
v1.32.3 |
v1.30.7 |
Please refer the individual release notes to get detailed information on each release.
Update Guide 🦮
Process
If you are using Cilium, read the steps below before proceeding.
- Just deploy as usual:
kustomize build katalog/calico | kubectl apply -f -
# OR
kustomize build katalog/tigera/on-prem | kubectl apply -f -
# OR
kustomize build katalog/cilium | kubectl apply -f -Cilium upgrade
Cilium suggested path expect a pre-flight check to be run before any upgrade.
- Create the resources for the check
kubectl create -f katalog/cilium/tasks/preflight.yaml- Ensure that the number of READY pods is the same number of Cilium pods running.
kubectl get daemonset -n kube-system | sed -n '1p;/cilium/p'
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
cilium 2 2 2 2 2 <none> 1h20m
cilium-pre-flight-check 2 2 2 2 2 <none> 7m15s
- Once the number of READY pods is equal, make sure the Cilium pre-flight deployment is also marked as READY 1/1.
If it shows READY 0/1, consult the CNP Validation section in the official docs and resolve issues with the deployment before continuing with the upgrade.
kubectl get deployment -n kube-system cilium-pre-flight-check -w
NAME READY UP-TO-DATE AVAILABLE AGE
cilium-pre-flight-check 1/1 1 0 12s
- 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.
kubectl delete -f cilium-preflight.yamlIf you are upgrading from previous versions, please refer to the v1.15.0 release notes.
Preview v1.16.0-rc.11
f10d03a
nutellinoit
Samuele Chiocca
Networking Core Module Release 1.16.0
Welcome to the latest release of the Networking module of Kubernetes Fury Distribution maintained by team SIGHUP.
This minor release updates some components and adds support to Kubernetes 1.28.
Component Images 🚢
| Component | Supported Version | Previous Version |
|---|---|---|
calico |
v3.27.0 |
v3.26.3 |
cilium |
v1.15.2 |
v1.14.3 |
ip-masq |
v2.8.0 |
No update |
tigera-operator |
v1.32.3 |
v1.30.7 |
Please refer the individual release notes to get detailed information on each release.
Update Guide 🦮
Process
If you are using Cilium, read the steps below before proceeding.
- Just deploy as usual:
kustomize build katalog/calico | kubectl apply -f -
# OR
kustomize build katalog/tigera/on-prem | kubectl apply -f -
# OR
kustomize build katalog/cilium | kubectl apply -f -Cilium upgrade
Cilium suggested path expect a pre-flight check to be run before any upgrade.
- Create the resources for the check
kubectl create -f katalog/cilium/tasks/preflight.yaml- Ensure that the number of READY pods is the same number of Cilium pods running.
kubectl get daemonset -n kube-system | sed -n '1p;/cilium/p'
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
cilium 2 2 2 2 2 <none> 1h20m
cilium-pre-flight-check 2 2 2 2 2 <none> 7m15s
- Once the number of READY pods is equal, make sure the Cilium pre-flight deployment is also marked as READY 1/1.
If it shows READY 0/1, consult the CNP Validation section in the official docs and resolve issues with the deployment before continuing with the upgrade.
kubectl get deployment -n kube-system cilium-pre-flight-check -w
NAME READY UP-TO-DATE AVAILABLE AGE
cilium-pre-flight-check 1/1 1 0 12s
- 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.
kubectl delete -f cilium-preflight.yamlIf you are upgrading from previous versions, please refer to the v1.15.0 release notes.
Preview v1.16.0-rc.8
80f39d3
nutellinoit
Samuele Chiocca
Networking Core Module Release 1.15.0
Welcome to the latest release of the Networking module of Kubernetes Fury Distribution maintained by team SIGHUP.
This minor release updates some components and adds support to Kubernetes 1.27.
Component Images 🚢
| Component | Supported Version | Previous Version |
|---|---|---|
calico |
v3.27.0 |
v3.26.1 |
cilium |
v1.15.2 |
v1.13.3 |
ip-masq |
v2.8.0 |
No update |
tigera-operator |
v1.32.3 |
v1.30.7 |
Please refer the individual release notes to get detailed information on each release.
Update Guide 🦮
Process
If you are using Cilium, read the steps below before proceeding.
- Just deploy as usual:
kustomize build katalog/calico | kubectl apply -f -
# OR
kustomize build katalog/tigera/on-prem | kubectl apply -f -
# OR
kustomize build katalog/cilium | kubectl apply -f -Cilium upgrade
Cilium suggested path expect a pre-flight check to be run before any upgrade.
- Create the resources for the check
kubectl create -f katalog/cilium/tasks/preflight.yaml- Ensure that the number of READY pods is the same number of Cilium pods running.
kubectl get daemonset -n kube-system | sed -n '1p;/cilium/p'
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
cilium 2 2 2 2 2 <none> 1h20m
cilium-pre-flight-check 2 2 2 2 2 <none> 7m15s
- Once the number of READY pods is equal, make sure the Cilium pre-flight deployment is also marked as READY 1/1.
If it shows READY 0/1, consult the CNP Validation section in the official docs and resolve issues with the deployment before continuing with the upgrade.
kubectl get deployment -n kube-system cilium-pre-flight-check -w
NAME READY UP-TO-DATE AVAILABLE AGE
cilium-pre-flight-check 1/1 1 0 12s
- 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.
kubectl delete -f cilium-preflight.yamlIf you are upgrading from previous versions, please refer to the v1.15.0 release notes.
Preview v1.16.0-rc5
Networking Core Module Release 1.15.0
Welcome to the latest release of the Networking module of Kubernetes Fury Distribution maintained by team SIGHUP.
This minor release updates some components and adds support to Kubernetes 1.27.
Component Images 🚢
| Component | Supported Version | Previous Version |
|---|---|---|
calico |
v3.27.0 |
v3.26.1 |
cilium |
v1.15.0 |
v1.13.3 |
ip-masq |
v2.8.0 |
v2.8.0 |
tigera-operator |
v1.32.3 |
v1.30.4 |
Please refer the individual release notes to get detailed information on each release.
Update Guide 🦮
Process
If you are using Cilium, read the steps below before proceeding.
- Just deploy as usual:
kustomize build katalog/calico | kubectl apply -f -
# OR
kustomize build katalog/tigera/on-prem | kubectl apply -f -
# OR
kustomize build katalog/cilium | kubectl apply -f -Cilium upgrade
Cilium suggested path expect a pre-flight check to be run before any upgrade.
- Create the resources for the check
kubectl create -f katalog/cilium/tasks/preflight.yaml- Ensure that the number of READY pods is the same number of Cilium pods running.
kubectl get daemonset -n kube-system | sed -n '1p;/cilium/p'
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
cilium 2 2 2 2 2 <none> 1h20m
cilium-pre-flight-check 2 2 2 2 2 <none> 7m15s
- Once the number of READY pods is equal, make sure the Cilium pre-flight deployment is also marked as READY 1/1.
If it shows READY 0/1, consult the CNP Validation section in the official docs and resolve issues with the deployment before continuing with the upgrade.
kubectl get deployment -n kube-system cilium-pre-flight-check -w
NAME READY UP-TO-DATE AVAILABLE AGE
cilium-pre-flight-check 1/1 1 0 12s
- 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.
kubectl delete -f cilium-preflight.yamlIf you are upgrading from previous versions, please refer to the v1.15.0 release notes.
Release v1.15.0
Networking Core Module Release 1.15.0
Welcome to the latest release of the Networking module of Kubernetes Fury Distribution maintained by team SIGHUP.
This minor release updates some components and adds support to Kubernetes 1.27.
Component Images 🚢
| Component | Supported Version | Previous Version |
|---|---|---|
calico |
v3.26.3 |
v3.26.1 |
cilium |
v1.14.3 |
v1.13.1 |
ip-masq |
v2.8.0 |
No update |
tigera-operator |
v1.30.7 |
v1.30.4 |
Please refer the individual release notes to get detailed information on each release.
Update Guide 🦮
Process
If you are using Cilium, read the steps below before proceeding.
- Just deploy as usual:
kustomize build katalog/calico | kubectl apply -f -
# OR
kustomize build katalog/tigera/on-prem | kubectl apply -f -
# OR
kustomize build katalog/cilium | kubectl apply -f -Cilium upgrade
Cilium suggested path expect a pre-flight check to be run before any upgrade.
- Create the resources for the check
kubectl create -f katalog/cilium/tasks/preflight.yaml- Make sure that the number of READY pods is the same as the number of RUNNING Cilium pods.
kubectl get daemonset -n kube-system | sed -n '1p;/cilium/p'
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
cilium 2 2 2 2 2 <none> 1h20m
cilium-pre-flight-check 2 2 2 2 2 <none> 7m15s
- Once the number of READY pods is equal, make sure the Cilium pre-flight deployment is also marked as READY 1/1.
If it shows READY 0/1, consult the CNP Validation section in the official docs and resolve issues with the deployment before continuing with the upgrade.
kubectl get deployment -n kube-system cilium-pre-flight-check -w
NAME READY UP-TO-DATE AVAILABLE AGE
cilium-pre-flight-check 1/1 1 0 12s
- 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.
kubectl delete -f cilium-preflight.yamlIf you are upgrading from previous versions, please refer to the v1.14.0 release notes.
Preview v1.15.0-rc.3
bf1c29a
nutellinoit
Samuele Chiocca
Networking Core Module Release 1.15.0
Welcome to the latest release of the Networking module of Kubernetes Fury Distribution maintained by team SIGHUP.
This minor release updates some components and adds support to Kubernetes 1.27.
Component Images 🚢
| Component | Supported Version | Previous Version |
|---|---|---|
calico |
v3.26.3 |
v3.26.1 |
cilium |
v1.14.3 |
v1.13.1 |
ip-masq |
v2.8.0 |
No update |
tigera-operator |
v1.30.7 |
v1.30.4 |
Please refer the individual release notes to get detailed information on each release.
Update Guide 🦮
Process
If you are using Cilium, read the steps below before proceeding.
- Just deploy as usual:
kustomize build katalog/calico | kubectl apply -f -
# OR
kustomize build katalog/tigera/on-prem | kubectl apply -f -
# OR
kustomize build katalog/cilium | kubectl apply -f -Cilium upgrade
Cilium suggested path expect a pre-flight check to be run before any upgrade.
- Create the resources for the check
kubectl create -f katalog/cilium/tasks/preflight.yaml- Make sure that the number of READY pods is the same as the number of RUNNING Cilium pods.
kubectl get daemonset -n kube-system | sed -n '1p;/cilium/p'
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
cilium 2 2 2 2 2 <none> 1h20m
cilium-pre-flight-check 2 2 2 2 2 <none> 7m15s
- Once the number of READY pods is equal, make sure the Cilium pre-flight deployment is also marked as READY 1/1.
If it shows READY 0/1, consult the CNP Validation section in the official docs and resolve issues with the deployment before continuing with the upgrade.
kubectl get deployment -n kube-system cilium-pre-flight-check -w
NAME READY UP-TO-DATE AVAILABLE AGE
cilium-pre-flight-check 1/1 1 0 12s
- 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.
kubectl delete -f cilium-preflight.yamlIf you are upgrading from previous versions, please refer to the v1.14.0 release notes.
Release v1.14.0
Networking Core Module Release 1.14.0
Welcome to the latest release of the Networking module of Kubernetes Fury Distribution maintained by team SIGHUP.
This minor release updates some components and adds support to Kubernetes 1.26.
Component Images 🚢
| Component | Supported Version | Previous Version |
|---|---|---|
calico |
v3.26.1 |
v3.25.0 |
cilium |
v1.13.3 |
v1.13.1 |
ip-masq |
v2.8.0 |
No update |
tigera-operator |
v1.30.4 |
v1.29.0 |
Please refer the individual release notes to get detailed information on each release.
Update Guide 🦮
Process
- Just deploy as usual:
kustomize build katalog/calico | kubectl apply -f -
# OR
kustomize build katalog/tigera/on-prem | kubectl apply -f -
# OR
kustomize build katalog/cilium | kubectl apply -f -If you are upgrading from previous versions, please refer to the v1.13.0 release notes.
Preview v1.14.0-rc.2
400282b
nutellinoit
Samuele Chiocca
Networking Core Module Release 1.14.0
Welcome to the latest release of the Networking module of Kubernetes Fury Distribution maintained by team SIGHUP.
This minor release updates some components and adds support to Kubernetes 1.26.
Component Images 🚢
| Component | Supported Version | Previous Version |
|---|---|---|
calico |
v3.26.1 |
v3.25.0 |
cilium |
v1.13.3 |
v1.13.1 |
ip-masq |
v2.8.0 |
No update |
tigera-operator |
v1.30.4 |
v1.29.0 |
Please refer the individual release notes to get detailed information on each release.
Update Guide 🦮
Process
- Just deploy as usual:
kustomize build katalog/calico | kubectl apply -f -
# OR
kustomize build katalog/tigera/on-prem | kubectl apply -f -
# OR
kustomize build katalog/cilium | kubectl apply -f -If you are upgrading from previous versions, please refer to the v1.13.0 release notes.