Kubernetes Fury Distribution Release v1.23.0
â This release contains issues, please use the version v1.23.1 instead ââ
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 Fury supports. 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 modulesAll the core modules have added
kubernetes
labels to easily identify it to be a part ofKFD
Provision for automated canonical definition generation
networking đĻ core module: v1.7.0 -> v1.8.0
- Update [Calico] from version
3.19.2
to3.21.3
and improvement to support the new version
- Update [Calico] from version
monitoring đĻ core module: v1.13.0 -> v1.14.0
- Update [Prometheus Operator] from version
0.50.0
to0.53.1
. - Update [Prometheus] from version
2.29.1
to2.32.1
. - Update [Grafana] from version
8.1.2
to8.3.3
. - Update [x509-exporter] from version
2.11.0
to2.12.1
. - Update [thanos] from version
0.22.0
to0.24.0
. - Update [node-exporter] from version
1.2.2
to1.3.1
. - Updates to various prometheus monitoring rules synching with kube-prometheus.
- Update [Prometheus Operator] from version
logging đĻ core module: v1.9.1 -> v1.10.0
- Update [fluentd] from version
1.14.0
to1.14.2
. - Update [fluent-bit] from version
1.8.2
to1.8.10
. - Update [elasticsearch] from version
7.13.3
to7.16.2
. - Update [kibana] from version
7.13.3
to7.16.2
. - Improve kibana index pattern injection via sidecar, remove readinessProbe
- several bug fixes on fluentd
- Update [fluentd] from version
ingress đĻ core module: v1.11.2 -> v1.12.0
- Update cert-manager CRDs as per upstream, dropping support for versions
< v1
- â ī¸
forecastle
is not supported in version1.23
of kubernetes - Update [forecastle] from version
1.0.66
to1.0.70
. - Update [nginx] ingress controller from version
1.0.0
to1.1.0
. - Update [cert-manager] from version
1.5.3
to1.6.1
.
- Update cert-manager CRDs as per upstream, dropping support for versions
dr đĻ core module: v1.8.0 -> v1.9.0
- Update [Velero] from version
1.6.3
to1.7.1
.- Upgrade velero-plugin-for-aws from
1.2.1
to1.3.0
- Upgrade velero-plugin-for-microsoft-azure from
1.2.1
to1.3.1
- Upgrade velero-plugin-for-gcp from
1.2.1
to1.3.0
- Upgrade velero-plugin-for-csi from
0.1.2
to0.2.0
- Upgrade velero-plugin-for-aws from
- Update [Velero] from version
OPA đĻ core module: v1.5.0 -> v1.6.0
- Add optional policy to protect accidental namespace deletion
- Update [Gatekeeper] from version
v3.6.0
tov3.7.0
. - Update [Gatekeeper Policy Manager]. Version
v0.5.1
.
Please refer to 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.
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