Skip to content

Releases: sighupio/fury-distribution

Release v1.5.1

19 Feb 10:40
Compare
Choose a tag to compare

Fury Distribution v1.5.1

Welcome to Fury v1.5.1. This distribution version includes a hotfix related to gathering metrics and logs from the
ingress module.

Please, carefully read the upgrade procedure before applying it.

Changelog

The most significant changes are listed below:

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

    • FIX: nginx ingress controller. Re-enable custom logging parser
    • FIX: cert-manager. Re-enable exposing metrics.
  • All the container images come from the SIGHUP registry to avoid rate limits.

Upgrade path

Procedure

Before upgrade delete some objects as they do not allow patch in place,
the procedure shouldn't cause downtime on the application side.

$ kubectl -n cert-manager delete deployment cert-manager-webhook cert-manager-cainjector cert-manager
deployment.apps "cert-manager-webhook" deleted
deployment.apps "cert-manager-cainjector" deleted
deployment.apps "cert-manager" deleted

Then, to upgrade the distribution from v1.5.0 to v1.5.1, 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.1/kind-config-v1.5.1.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.1/fury-distribution-v1.5.1.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

Release v1.5.0

07 Jan 15:00
Compare
Choose a tag to compare

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

Release v1.4.0

29 Sep 17:23
Compare
Choose a tag to compare

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:

Upgrade path

Important note

As mentioned above, it is really important to follow each core module upgrade path:

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

Release v1.2.0

20 May 09:01
Compare
Choose a tag to compare

Release Notes

Welcome to the Fury Distribution v1.2.0. In this new version we had addressed some logging updates along with new stability and observability improvements while supporting three different Kubernetes Upstream Version: 1.14, 1.15 and 1.16.

Changelog

Most important changes are listed below:

  • networking 📦 core module: v1.2.0 -> v1.2.1
    • Exposed calico metrics.
  • monitoring 📦 core module: v1.6.0 -> v1.6.1
    • New calico dashboard.
  • logging 📦 core module: v1.2.1 -> v1.3.0
    • Updated cerebro from 0.8.1 to 0.8.5
      • Added healthcheck to cerebro container.
    • Updated fluentd from 1.7.2 to 1.10.2
      • Improved log parsing.
      • Added nginx ingress controller parser.
      • Added healthcheck to fluentd container.
    • Updated elasticsearch from 6.4.1 to 6.8.6
    • Updated kibana from 6.4.1 to 6.8.6
      • Improved security in Kibana container.
      • Added healthcheck to Kibana container.
    • Updated curator from 5.6.0 to 5.8.1
  • ingress 📦 core module: v1.6.0 -> v1.6.1
    • Enabled nginx ingress logs for default backend.
  • dr 📦 core module: v1.2.0 -> v1.3.0
    • Decoupled Velero Schedules.

Release v1.1.0

17 Apr 10:07
Compare
Choose a tag to compare

Release Notes

Welcome to the Fury Distribution v1.1.0. This release includes some awesome features like the gatekeeper package while supporting three different Kubernetes Upstream Version: 1.14, 1.15 and 1.16

Changelog

Most important changes are listed below:

Release v1.0.0

18 Feb 14:46
Compare
Choose a tag to compare
Add overwrite to github releases