Release v1.4.0
Fury Distribution v1.4.0
Welcome to the Fury Distribution v1.4.0. In this new version, we had addressed the update of multiples
packages that belong to the distribution. All of them have been pushed to the latest stable release of each.
It includes testing (as tech preview) against Kubernetes v1.19.0
.
The team has been working to make the release upgrade as simple as possible, so read carefully the upgrade path of each
core module listed below along with the upgrade path of the distribution.
This release includes some major packages releases like Grafana v7, cert-manager v1, and ElasticSearch v7.
All of them include a lot of nice improvements. Along with the Grafana update, we include a complete refactor to
the pre-defined dashboards. Now you will find only those dashboards that fit in your environment.
Changelog
The most important changes are listed below:
- networking 📦 core module: v1.3.0 -> v1.4.0
- Kubernetes
1.19
Tech preview. - Update Calico from version
3.12
to3.16
.
- Kubernetes
- monitoring 📦 core module: v1.8.0 -> v1.10.2
- Kubernetes
1.19
Tech preview. - Update Prometheus Operator from version
0.37.0
to0.42.0
. - Update Prometheus from version
2.16.0
to2.21.0
. - Update Alertmanager from version
0.20.0
to0.21.0
. - Update Grafana from version
6.6.2
to7.1.5
. - Update node-exporter from version
0.3.6
to1.9.1
. - Update kube-state-metrics from version
1.9.5
to1.9.7
. - Update metrics-server from version
0.3.6
to0.3.7
. - Update goldpinger from
2.0.0
to3.0.0
. - Add kube-proxy-metrics to expose
kube-proxy
metrics on any environment. - Add new Grafana (internals) dashboard.
- Refactor default dashboards. Changes the previous default behavior.
- Kubernetes
- logging 📦 core module: v1.5.0 -> v1.6.0
- Kubernetes
1.19
Tech preview. - Update Cerebro from version
0.8.5
to0.9.2
. - Update fluentd from version
1.10.2
to1.11.2
. - Update fluent-bit from version
1.4.4
to1.5.6
. - Update kibana from version
6.8.8
to7.9.1
. - Update elasticsearch from version
6.8.8
to7.9.1
.
- Kubernetes
- ingress 📦 core module: v1.7.0 -> v1.8.1
- Kubernetes
1.19
Tech preview. - Update forecastle from version
1.0.42
to1.0.57
. - Update nginx ingress controller from version
0.30.0
to0.35.0
. - Update cert-manager from version
0.14.1
to1.0.1
.
- Kubernetes
- dr 📦 core module: v1.4.0 -> v1.5.0
- Kubernetes
1.19
Tech preview. - Update Velero from version
1.3.1
to1.5.1
.- Increase Velero default limit to 1Gi.
- Add velero Grafana Dashboard
- Update velero-restic from version
1.3.1
to1.5.1
. - Update velero plugins from version
1.0.1
to1.1.0
. - Update velero's minio server from version
RELEASE.2020-01-25T02-50-51Z
toRELEASE.2020-09-17T04-49-20Z
.
- Kubernetes
- OPA 📦 core module: v1.1.0 -> v1.2.1
- Kubernetes
1.19
Tech preview. - Update Gatekeeper from version
v3.1.0-beta.9
tov3.1.1
.- Enable HA
- Kubernetes
Upgrade path
Important note
As mentioned above, it is really important to follow each core module upgrade path:
- Read and follow the upgrade path of the monitoring module.
- Read and follow the upgrade path of the logging module.
- Read and follow the upgrade path of the ingress module.
Be sure you completed all required action before continuing with the upgrade procedure
Procedure
To upgrade this distribution from v1.3.0
to v1.4.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.9.0 go1.15.2 darwin/amd64
$ curl -Ls https://github.com/sighupio/fury-distribution/releases/download/v1.4.0/kind-config-v1.4.0.yml | kind create cluster --config -
Creating cluster "kind" ...
✓ Ensuring node image (kindest/node:v1.19.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.4.0/fury-distribution-v1.4.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