Releases: sighupio/module-networking
Release v2.1.0
Networking Core Module Release v2.1.0
Welcome to the latest release of the Networking
module of SIGHUP Distribution
maintained by team SIGHUP by ReeVo.
This release updates several packages to the latest versions available for new features, bug fixes and improved security, it also drops compatibility with Kubernetes 1.28 and introduces compatibility with Kubernetes 1.32.
Bug fixes 🐞
- [#87] Extended Cilium's mTLS selfg-signed CA certificated duration to 10 years instead of having them expire before the peer certificates to avoid breaking communication. See the update guide below for more information on additional steps needed after updating.
Component Images 🚢
Component | Supported Version | Previous Version |
---|---|---|
cilium |
v1.17.2 |
v1.16.3 |
ip-masq |
v2.8.0 |
No update |
tigera-operator |
v1.36.5 |
v1.36.1 |
Please refer the individual release notes to get detailed information on each release.
Breaking Changes 💔
- None
Update Guide 🦮
Process
- Just deploy as usual:
kustomize build katalog/tigera/on-prem | kubectl apply --server-side -f -
# OR
kustomize build katalog/cilium | kubectl apply --server-side -f -
- (Cilium only) After applying the new version, you will need to manually trigger the renewal of the mTLS certificates for Cilium:
cmctl renew -n kube-system hubble-relay-client-certs
cmctl renew -n kube-system hubble-server-certs
Note: you will need cert-manager's CLI cmctl
installed.
Preview v2.1.0-rc.1
Networking Core Module Release v2.1.0
Welcome to the latest release of the Networking
module of Kubernetes Fury Distribution
maintained by team SIGHUP.
This release updates several packages to the latest versions available for new features, bug fixes and improved security, it also drops compatibility with Kubernetes 1.28 and introduces compatibility with Kubernetes 1.32.
Bug fixes 🐞
- [#87] Extended Cilium's mTLS selfg-signed CA certificated duration to 10 years instead of having them expire before the peer certificates to avoid breaking communication. See the update guide below for more information on additional steps needed after updating.
Component Images 🚢
Component | Supported Version | Previous Version |
---|---|---|
cilium |
v1.17.2 |
v1.16.3 |
ip-masq |
v2.8.0 |
No update |
tigera-operator |
v1.36.5 |
v1.36.1 |
Please refer the individual release notes to get detailed information on each release.
Breaking Changes 💔
- None
Update Guide 🦮
Process
- Just deploy as usual:
kustomize build katalog/tigera/on-prem | kubectl apply --server-side -f -
# OR
kustomize build katalog/cilium | kubectl apply --server-side -f -
- (Cilium only) After applying the new version, you will need to manually trigger the renewal of the mTLS certificates for Cilium:
cmctl renew -n kube-system hubble-relay-client-certs
cmctl renew -n kube-system hubble-server-certs
Note: you will need cert-manager's CLI cmctl
installed.
Release v2.0.0
Networking Core Module Release 2.0.0
Welcome to the latest release of the Networking
module of Kubernetes Fury Distribution
maintained by team SIGHUP.
This major release updates some components and adds support to Kubernetes 1.30 and 1.31
Component Images 🚢
Component | Supported Version | Previous Version |
---|---|---|
calico |
Package removed in favor of tigera-operator | v3.27.0 |
cilium |
v1.16.3 |
1.15.2 |
ip-masq |
v2.8.0 |
No update |
tigera-operator |
v1.36.1 |
v1.32.7 |
Please refer the individual release notes to get detailed information on each release.
Breaking Changes 💔
- Manifest calico installation has been removed in favour of the Tigera Operator. There is a migration guide.
Update Guide 🦮
Process
- Just deploy as usual:
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.17.0
release notes.
Preview v2.0.0-rc.2
Networking Core Module Release 2.0.0
Welcome to the latest release of the Networking
module of Kubernetes Fury Distribution
maintained by team SIGHUP.
This major release updates some components and adds support to Kubernetes 1.30 and 1.31
Component Images 🚢
Component | Supported Version | Previous Version |
---|---|---|
calico |
Package removed in favor of tigera-operator | v3.27.0 |
cilium |
v1.16.3 |
1.15.2 |
ip-masq |
v2.8.0 |
No update |
tigera-operator |
v1.36.1 |
v1.32.7 |
Please refer the individual release notes to get detailed information on each release.
Breaking Changes 💔
- Manifest calico installation has been removed in favor of the Tigera Operator. There is a migration guide.
Update Guide 🦮
Process
- Just deploy as usual:
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.17.0
release notes.
Preview v2.0.0-rc.1
Networking Core Module Release 2.0.0
Welcome to the latest release of the Networking
module of Kubernetes Fury Distribution
maintained by team SIGHUP.
This major release updates some components and adds support to Kubernetes 1.30 and 1.31
Component Images 🚢
Component | Supported Version | Previous Version |
---|---|---|
cilium |
v1.16.3 |
1.15.2 |
ip-masq |
v2.8.0 |
No update |
tigera-operator |
v1.36.1 |
v1.32.7 |
Please refer the individual release notes to get detailed information on each release.
Breaking Changes 💔
- Manifest calico installation has been removed in favor of the Tigera Operator. There is a migration guide.
Update Guide 🦮
Process
- Just deploy as usual:
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.17.0
release notes.
Preview v2.0.0-rc.0
Networking Core Module Release 2.0.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 |
---|---|---|
cilium |
v1.15.2 |
No update |
ip-masq |
v2.8.0 |
No update |
tigera-operator |
v1.36.1 |
v1.32.7 |
Please refer the individual release notes to get detailed information on each release.
Breaking Changes 💔
- Manifest calico installation has been removed in favor of the Tigera Operator. There is a migration guide.
Update Guide 🦮
Process
- Just deploy as usual:
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.17.0
release notes.
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
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.yaml
If you are upgrading from previous versions, please refer to the v1.15.0
release notes.
Preview v1.16.0-rc.11
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.yaml
If you are upgrading from previous versions, please refer to the v1.15.0
release notes.