Skip to content

Release v1.23.0
Compare
Choose a tag to compare
@SIGHUP-C-3PO SIGHUP-C-3PO released this 28 Jan 17:36
v1.23.0
6d5939b
This commit was created on github.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

❌ This release contains issues, please use the version v1.23.1 instead ❌

Kubernetes Fury Distribution Release v1.23.0

Welcome to the KFD release v1.23.0. From this release on, Fury follows a
different versioning schema. KFD version now will closely follow the version of
the latest Kubernetes release that is supported by Fury. So this is the first
release that supports kubernetes runtime v1.23.0.

This distribution is maintained with ❤️ by the team SIGHUP,
and is battle tested in production environments.

This new release of KFD features a bundle of all the core modules supported by
Fury with enhancements and bug fixes. Alongside, Fury gets a new face with this
release. We would like to introduce our brand new
documentation site with this release.

New Features

Core Module Updates

  • Kubernetes 1.23 Tech preview on all modules

  • All the core modules have added kubernetes labels to easily identify it to
    be a part of KFD

  • Updated documentation for every core module

  • Provision for automated canonical definition generation

  • networking 📦 core module: v1.7.0 -> v1.8.0

    • Update [Calico] from version 3.19.2 to 3.21.3 and improvement to support
      the new version

  • monitoring 📦 core module: v1.13.0 -> v1.14.0

    • Update [Prometheus Operator] from version 0.50.0 to 0.53.1.
    • Update [Prometheus] from version 2.29.1 to 2.32.1.
    • Update [Grafana] from version 8.1.2 to 8.3.3.
    • Update [x509-exporter] from version 2.11.0 to 2.12.1.
    • Update [thanos] from version 0.22.0 to 0.24.0.
    • Update [node-exporter] from version 1.2.2 to 1.3.1.
    • Updates to various prometheus monitoring rules synching with kube-prometheus.

  • logging 📦 core module: v1.9.1 -> v1.10.0

    • Update [fluentd] from version 1.14.0 to 1.14.2.
    • Update [fluent-bit] from version 1.8.2 to 1.8.10.
    • Update [elasticsearch] from version 7.13.3 to 7.16.2.
    • Update [kibana] from version 7.13.3 to 7.16.2.
    • Improve kibana index pattern injection via sidecar, remove readinessProbe
    • several bug fixes on fluentd

  • ingress 📦 core module: v1.11.2 -> v1.12.0

    • Update cert-manager CRDs as per upstream, dropping support for versions < v1
    • Update [forecastle] from version 1.0.66 to 1.0.73.
    • Update [nginx] ingress controller from version 1.0.0 to 1.1.0.
    • Update [cert-manager] from version 1.5.3 to 1.6.1.

  • dr 📦 core module: v1.8.0 -> v1.9.0

    • Deprecation to eks-velero module in favor of aws-velero
    • Update [Velero] from version 1.6.3 to 1.7.1.
      • Upgrade velero-plugin-for-aws from 1.2.1 to 1.3.0
      • Upgrade velero-plugin-for-microsoft-azure from 1.2.1 to 1.3.1
      • Upgrade velero-plugin-for-gcp from 1.2.1 to 1.3.0
      • Upgrade velero-plugin-for-csi from 0.1.2 to 0.2.0

  • OPA 📦 core module: v1.5.0 -> v1.6.0

    • Add optional policy to protect accidental namespace deletion
    • Update [Gatekeeper] from version v3.6.0 to v3.7.0.
    • Update [Gatekeeper Policy Manager]. Version v0.5.1.

Please refer the individual release notes for detailed information

Upgrade path

Katalog Procedure

To upgrade this distribution from v1.7.x to v1.23.0, you need to download this new version, vendor the dependencies,
finally applying the kustomize project.

furyctl vendor -H
kustomize build . | kubectl apply -f -

NOTE: The upgrade takes some minutes (depends on the cluster size), and you should expect some downtime during
the upgrade process.

Terraform Procedure

Test it

If you want to test the distribution in a test environment, spin up a
kind cluster, then deploy all rendered manifests.

$ kind version
kind v0.11.0 go1.16.4 darwin/amd6   4
$ curl -Ls https://github.com/sighupio/fury-distribution/releases/download/v1.23.0/katalog/tests/config/kind-config | kind create cluster --image registry.sighup.io/fury/kindest/node:v1.23.0 --config -
Creating cluster "kind" ...
 ✓ Ensuring node image (kindest/node:v1.20.1) 🖼
 ✓ Preparing nodes 📦 📦
 ✓ Writing configuration 📜
 ✓ Starting control-plane 🕹️
 ✓ Installing StorageClass 💾
 ✓ Joining worker nodes 🚜
Set kubectl context to "kind-kind"
You can now use your cluster with:

kubectl cluster-info --context kind-kind

Have a question, bug, or feature request? Let us know! https://kind.sigs.k8s.io/#community 🙂
$ kubectl apply -f https://github.com/sighupio/fury-distribution/releases/download/v1.23.0/fury-distribution-v1.23.0.yml
namespace/cert-manager created
namespace/gatekeeper-system created
namespace/ingress-nginx created
namespace/logging created
namespace/monitoring created
customresourcedefinition.apiextensions.k8s.io/alertmanagers.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/bgpconfigurations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/bgppeers.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/blockaffinities.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/certificaterequests.cert-manager.io created
customresourcedefinition.apiextensions.k8s.io/certificates.cert-manager.io created
customresourcedefinition.apiextensions.k8s.io/challenges.acme.cert-manager.io created
customresourcedefinition.apiextensions.k8s.io/clusterinformations.crd.projectcalico.org created
<TRUNCATED OUTPUT>

NOTE: Run kubectl apply multiple times until you see no errors in the console

Assets 9
Loading