Flux2 came with its new update a while ago, and it is sheer exciting for the users because it brought a lot of new features. It also made a lot of new enhancements and updates. We will take a look at the entire catalogue in this article. So, without further a due, let’s start.
What is Flux?
Flux is a Cloud Native Computing Foundation (CNCF) project. It is a tool that helps keep Kubernetes clusters in sync with sources of configuration such as Git Repositories. It also helps in automating updates to the configuration when there is a new code to deploy.
Highlights of the Release
The new release comes with the improvement of the Flux garbage collector. It can now work nicely with other controllers such as Strimzi Kafka Operator, Redis Operator, Prometheus Operator, etc. Another significant and beneficial change that we can find in this latest release is the update of the notification controller. The Notification controller will now be able to send alerts to Telegram, Lark and Matrix, in addition to many others. The last highlight of the release is the updated version of the Kustomize controller. The devs have updated the Kustomize controller on a par with the latest Kustomize release, v4.3.0.
Version 0.17.0 brings the update of toolkit components. With this new release, we can see the addition of the logs, and also we can see the addition of two flags, namely
–since-time. The latest release also removed the use of deprecated io/ioutil. We can also see the use of shared envTest for unit tests which will be helpful to the users.
With this new update, we can see the renaming of trace test golden files. Again, the latest release makes the test harness more flexible with functions. Also, we can see the moving of arm64 e2e to Go tests. The devs have fixed the issue where there will be no substitution issue in kustomize for azure credentials sync. The new update also brings the wiring of kubebuilder assets to the envtest bin. Also, with the release of this version, we can observe the removal of fakeclient and use testenv for flux cmd tests. We can again see the refactoring of e2e tests. The devs have updated the links to the calendar and resources, which will help users browse the resources efficiently. We can also see the addition of an e2e test case for check
--pre. Lastly, the new release brings the implementation of testEnv for e2e tests.
The release of version 0.17.0 brings the new Flagger version of 1.13.0. This Flagger release comes with the support for Open Service Mesh. For more details, please have a look at the OSM Progressive Delivery tutorial. Starting with this version, we can see the signing of Flagger container images with sigstore/cosign. For more details on this topic, see the Flagger cosign docs.
Flux in Operator Hub
A piece of exciting news that came with the latest release is that Flux Operator is now on the Operator Hub, and it supports Red Hat OpenShift version 4.6, 4.7, and 4.8. We can install Flux Operator for OpenShift directly via the OpenShift web console on the Operators tab. It also works on OKD, which is the Community Distribution that powers OpenShift. Flux on OpenShift has several features such as one-click installation, automatic upgrades, and Flux resources UI.
So, we finally have come to the end of this article. We have discussed all of the changes that took place with the release of version 0.17.0. You can contribute to this new version by clicking here or can install the latest version by clicking here. So, what are you waiting for?
Read more of our blogs below. Happy learning!