Preview v1.16.0-rc.8

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

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

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

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.

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

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

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

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

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.

kubectl delete -f cilium-preflight.yaml

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

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

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

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

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.

kubectl delete -f cilium-preflight.yaml

If you are upgrading from previous versions, please refer to the v1.14.0 release notes.

Preview v1.15.0-rc.3

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.

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

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

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

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.

kubectl delete -f cilium-preflight.yaml

If 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

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.13.0 release notes.

Preview v1.14.0-rc.2

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

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.13.0 release notes.

Release v1.13.0

Networking Core Module Release 1.13.0

Welcome to the latest release of the Networking module of Kubernetes Fury Distribution maintained by team SIGHUP.

This is a minor release adding Cilium as a package! it also fixes the namespace where the Grafana dashboards are deployed and they get their own folder in Grafana's UI.

Component Images 🚢

Component	Supported Version	Previous Version
calico	v3.25.0	No update
cilium	v1.13.1	New Package
ip-masq	v2.8.0	No update
tigera-operator	v1.29.0	No update

Please refer the individual release notes to get detailed information on each release.

Update Guide 🦮

Process

From this version, you can start using Cilium as the CNI for a Kubernetes Fury on-premises cluster!

If you are upgrading from v1.12.2, there are no significant changes, you need to:

1. delete the Grafana dashboard configmap:

kubectl delete configmap networking-grafana-dashboard -n default

2. 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.12.0 release notes.

Release v1.12.2

Networking Core Module Release 1.12.2

Welcome to the latest release of Networking module of Kubernetes Fury Distribution maintained by team SIGHUP.

This is a patch release that fixes one issue with tigera eks-policy-only package and operator.

Component Images 🚢

Component	Supported Version	Previous Version
calico	v3.25.0	No update
ip-masq	v2.8.0	No update
tigera-operator	v1.29.0	No update

Please refer the individual release notes to get detailed information on each release.

Bug Fixes and Changes 🐛

• #61 add trailing slash to tigera operator installation's .spec.registry
• #60 fix kustomization.yaml to patch the sighup registry correctly

Update Guide 🦮

Process

If you are upgrading from version v1.12.1 to v1.12.2 you need to download this new version and then apply the kustomize project as shown below.

kustomize build katalog/tigera/eks-policy-only | kubectl apply -f -
# OR
kustomize build katalog/tigera/on-prem | kubectl apply -f -

If you are upgrading from previous versions, please refer to the v1.11.0 release notes.

Release v1.12.1

Networking Core Module Release 1.12.1

Welcome to the latest release of Networking module of Kubernetes Fury Distribution maintained by team SIGHUP.

This is a patch release that fixes one issue with tigera eks-policy-only package.

Component Images 🚢

Component	Supported Version	Previous Version
calico	v3.25.0	No update
ip-masq	v2.8.0	No update
tigera-operator	v1.29.0	No update

Please refer the individual release notes to get detailed information on each release.

Bug Fixes and Changes 🐛

• #55 change default registry from docker hub to registry.sighup.io.

Update Guide 🦮

Process

If you are upgrading from version v1.12.0 to v1.12.1 you need to download this new version and then apply the kustomize project as shown below.

kustomize build katalog/tigera/eks-policy-only | kubectl apply -f -

If you are upgrading from previous versions, please refer to the v1.11.0 release notes.

Release v1.12.0

Networking Core Module Release 1.12.0

Welcome to the latest release of Networking module of Kubernetes Fury Distribution maintained by team SIGHUP.

This is a minor release that updates most components for compatibility with Kubernetes v1.25.

Component Images 🚢

Component	Supported Version	Previous Version
calico	v3.25.0	3.24.1
ip-masq	v2.8.0	No update
tigera-operator	v1.29.0	1.28.1

Please refer the individual release notes to get detailed information on each release.

Update Guide 🦮

Process

If you are upgrading from version v1.11.0 to v1.12.0 you need to download this new version and then apply the kustomize project as shown below.

# To deploy Calico
kustomize build katalog/calico | kubectl apply -f-
# To deploy ipmasq
kusomize build katalog/ip-masq | kubectl apply -f-

If you are upgrading from previous versions, please refer to the v1.11.0 release notes.