Skip to content

Release v1.15.0
Compare
Choose a tag to compare
@SIGHUP-C-3PO SIGHUP-C-3PO released this 27 Nov 11:55
· 62 commits to main since this release
v1.15.0
de9de86
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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
  1. 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
  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.14.0 release notes.

Assets 5