Skip to content

Release v1.5.0
Compare
Choose a tag to compare
@angelbarrera92 angelbarrera92 released this 07 Jan 15:00
· 1296 commits to main since this release
v1.5.0
6461b01

Fury Distribution v1.5.0

Welcome to the Fury Distribution v1.5.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.20.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.

Changelog

The most important changes are listed below:

  • networking 📦 core module: v1.4.0 -> v1.5.0

    • Kubernetes 1.20 Tech preview.
    • Update Calico from version 3.16.1 to 3.17.1.

  • monitoring 📦 core module: v1.10.1 -> v1.11.0

  • logging 📦 core module: v1.6.0 -> v1.7.0

    • Kubernetes 1.20 Tech preview.
    • Update Cerebro from version 0.9.2 to 0.9.3.
    • Update fluentd from version 1.11.2 to 1.11.5.
    • Update fluent-bit from version 1.5.6 to 1.6.9.
    • Update elasticsearch from version 7.9.1 to 7.10.1.
    • Update kibana from version 7.9.1 to 7.10.1.

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

    • Kubernetes 1.20 Tech preview.
    • Update forecastle from version 1.0.57 to 1.0.61.
    • Update nginx ingress controller from version 0.35.0 to 0.43.0.
    • Update cert-manager from version 1.0.1 to 1.1.0.

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

    • Kubernetes 1.20 Tech preview.
    • Update velero AWS module.

  • OPA 📦 core module: v1.2.1 -> v1.3.0

  • All the container images come from the SIGHUP registry to avoid rate limits.

Upgrade path

Procedure

To upgrade this distribution from v1.4.0 to v1.5.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.5.0/kind-config-v1.5.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.5.0/fury-distribution-v1.5.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 8
Loading