Skip to content

Releases: sighupio/fury-kubernetes-networking

Release v2.0.0

27 Nov 17:19
@SIGHUP-C-3PO SIGHUP-C-3PO
v2.0.0
a18e4ca
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Release v2.0.0 Latest
Latest

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 💔

  1. Manifest calico installation has been removed in favour of the Tigera Operator. There is a migration guide.

Update Guide 🦮

Process

  1. 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.

Assets 5
Loading

Preview v2.0.0-rc.2

20 Nov 17:21
@SIGHUP-C-3PO SIGHUP-C-3PO
v2.0.0-rc.2
f415b00
This commit was signed with the committer’s verified signature.
nutellinoit Samuele Chiocca
GPG key ID: 9A702ECAD84C6874
Learn about vigilant mode.
Compare
Choose a tag to compare
Preview v2.0.0-rc.2 Pre-release
Pre-release

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 💔

  1. Manifest calico installation has been removed in favor of the Tigera Operator. There is a migration guide.

Update Guide 🦮

Process

  1. 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.

Assets 5
Loading

Preview v2.0.0-rc.1

19 Nov 15:56
@SIGHUP-C-3PO SIGHUP-C-3PO
v2.0.0-rc.1
7865667
This commit was signed with the committer’s verified signature.
nutellinoit Samuele Chiocca
GPG key ID: 9A702ECAD84C6874
Learn about vigilant mode.
Compare
Choose a tag to compare
Preview v2.0.0-rc.1 Pre-release
Pre-release

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 💔

  1. Manifest calico installation has been removed in favor of the Tigera Operator. There is a migration guide.

Update Guide 🦮

Process

  1. 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.

Assets 5
Loading

Preview v2.0.0-rc.0

19 Nov 15:29
@SIGHUP-C-3PO SIGHUP-C-3PO
v2.0.0-rc.0
67f12d7
This commit was signed with the committer’s verified signature.
nutellinoit Samuele Chiocca
GPG key ID: 9A702ECAD84C6874
Learn about vigilant mode.
Compare
Choose a tag to compare
Preview v2.0.0-rc.0 Pre-release
Pre-release

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 💔

  1. Manifest calico installation has been removed in favor of the Tigera Operator. There is a migration guide.

Update Guide 🦮

Process

  1. 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.

Assets 5
Loading

Release v1.17.0

22 Apr 15:52
@SIGHUP-C-3PO SIGHUP-C-3PO
v1.17.0
b626bc6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
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

  1. 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.

Assets 5
Loading

Preview v1.16.1-rc.3

18 Apr 13:09
@SIGHUP-C-3PO SIGHUP-C-3PO
v1.16.1-rc.3
63c808e
This commit was signed with the committer’s verified signature.
nutellinoit Samuele Chiocca
GPG key ID: 9A702ECAD84C6874
Learn about vigilant mode.
Compare
Choose a tag to compare
Preview v1.16.1-rc.3 Pre-release
Pre-release

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

  1. 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.

Assets 5
Loading

Release v1.16.0

27 Mar 10:35
@SIGHUP-C-3PO SIGHUP-C-3PO
v1.16.0
c1c9200
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
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.

  1. 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.

  1. Create the resources for the check
kubectl create -f katalog/cilium/tasks/preflight.yaml
  1. 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
  1. 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
  1. 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.

Assets 5
Loading

Preview v1.16.0-rc.11

27 Mar 10:23
@SIGHUP-C-3PO SIGHUP-C-3PO
v1.16.0-rc.11
f10d03a
This commit was signed with the committer’s verified signature.
nutellinoit Samuele Chiocca
GPG key ID: 9A702ECAD84C6874
Learn about vigilant mode.
Compare
Choose a tag to compare
Preview v1.16.0-rc.11 Pre-release
Pre-release

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.

  1. 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.

  1. Create the resources for the check
kubectl create -f katalog/cilium/tasks/preflight.yaml
  1. 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
  1. 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
  1. 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.

Assets 5
Loading

Preview v1.16.0-rc.8

15 Mar 16:21
@SIGHUP-C-3PO SIGHUP-C-3PO
v1.16.0-rc.8
80f39d3
This commit was signed with the committer’s verified signature.
nutellinoit Samuele Chiocca
GPG key ID: 9A702ECAD84C6874
Learn about vigilant mode.
Compare
Choose a tag to compare
Preview v1.16.0-rc.8 Pre-release
Pre-release

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.

  1. 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.

  1. Create the resources for the check
kubectl create -f katalog/cilium/tasks/preflight.yaml
  1. 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
  1. 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
  1. 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.

Assets 5
Loading

Preview v1.16.0-rc5

01 Mar 11:50
@SIGHUP-C-3PO SIGHUP-C-3PO
v1.16.0-rc5
252d230
Compare
Choose a tag to compare
Preview v1.16.0-rc5 Pre-release
Pre-release

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.

  1. 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.

  1. Create the resources for the check
kubectl create -f katalog/cilium/tasks/preflight.yaml
  1. 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
  1. 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
  1. 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.

Assets 5
Loading