Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Pre-)Release v2.2.0 Blog #1733

Closed
wants to merge 6 commits into from
Closed

(Pre-)Release v2.2.0 Blog #1733

Changes from 5 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
3689df3
Release v2.2.0 Blog (draft)
Dec 5, 2023
48d5242
If you need help with anything...
Dec 6, 2023
49d7c7d
add detail about Helm update
Dec 7, 2023
8a5a158
about image-automation-controller dependencies
Dec 7, 2023
4537b9c
grammar, formatting
Dec 7, 2023
30772e6
move references to unreleased docs to invisible
Dec 7, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 42 additions & 0 deletions content/en/blog/2023-12-07-flux-release-around-the-corner/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
---
author: kingdonb
date: 2023-12-07 00:00:00+00:00
title: Flux v2.2 release is just around the corner!
description: "Flux v2.2.0: Major Helm improvements!"
url: /blog/2023/12/flux-v2-2-release-around-the-corner/
tags: [announcement]
resources:
- src: "**.{png,jpg}"
title: "Image #:counter"
---

Now that Flux has reached General Availability, there are planned 3 minor releases per year. So, the maintainer team has been hard at work to create this Flux v2.2.0 release, which is slated to come out next week! Keep your eye out!

While this next release addresses hundreds of issues and has many improvements that will be covered in more detail by a follow-up blog post, we want to highlight one crowning achievement of the next release: Flux helm-controller's reconciliation model has undergone a significant overhaul, this is the one we've all been waiting for!

We hope many Flux users will rejoice in the improvements of the updated helm-controller, and that you'll all update to the latest release. This will help, in particular, with the issue of how the automatic recovery of Helm releases could occasionally get stuck in a pending state.

Two new controls become available in the CLI (and as annotations) that can either [force](https://github.com/fluxcd/helm-controller/blob/64fed65148342578c1ed4b2155cd81852c54557a/docs/spec/v2beta2/helmreleases.md#forcing-a-release) or [reset](https://github.com/fluxcd/helm-controller/blob/64fed65148342578c1ed4b2155cd81852c54557a/docs/spec/v2beta2/helmreleases.md#resetting-remediation-retries) the `HelmRelease`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This refers to documentation which hasn't been merged, my intent was to use the information to enrich the post. Not to link to it.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe the best compromise here is to just not include the links, until the release is out, and then I'll add links in a follow-up commit. (This feedback right here is the reason why I thought it would actually be simpler to release this blog concurrent with the actual release, not ahead-of-time. How do we refer to these features without linking any docs?)

Of course we can just remove the links, if we're happy with the text. This is the pre-release blog, so I'm not sure how else we can make it comprehensive except to link to some docs which are not released yet.

We could try linking to pull requests instead of linking to docs that are unreleased? WDYT

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've pulled those unpublished references out into the footer so I don't lose track of them, but they are not links anymore.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You refer to the features by providing a brief overview of what will be added or changed, or showcasing it. This would not require references to documentation.

I continue to feel that without doing any of this, the blog post is just void and doesn't warn people up in any way, nor would it tell people more than what is stated in the release notes. Which means I still do not get the point of publishing this in its current form.


In addition, the latest release improves the observability of the Helm release status by reflecting more detailed historic information in the [describe](https://github.com/fluxcd/helm-controller/blob/64fed65148342578c1ed4b2155cd81852c54557a/docs/spec/v2beta2/helmreleases.md#describe-the-helmrelease) output and in the [status](https://github.com/fluxcd/helm-controller/blob/64fed65148342578c1ed4b2155cd81852c54557a/docs/spec/v2beta2/helmreleases.md#history) of the HelmRelease object.

The long-awaited [Drift Detection](https://github.com/fluxcd/helm-controller/blob/64fed65148342578c1ed4b2155cd81852c54557a/docs/spec/v2beta2/helmreleases.md#drift-detection) feature also received an update. Having first been introduced and tested as a global feature flag, the new release introduces the ability to enable drift detection on a per-object basis.

This includes the option to ignore drift in specific fields using Kustomize-like target selectors and JSON pointer paths, which helps to reduce the noise of notifications and prevent upgrades from infinitely cycling. Helm Drift detection and correction also is no longer experimental starting in this release. To opt-in through `HelmRelease.spec.driftDetection` in the `v2beta2` API, enable Drift Detection mode.

An [example from the docs](https://github.com/fluxcd/helm-controller/blob/64fed65148342578c1ed4b2155cd81852c54557a/docs/spec/v2beta2/helmreleases.md#ignore-rules) below shows how Drift Detection can be configured to work with an HPA, where some drift is always expected to occur in the `spec.replicas` field:

```yaml
spec:
driftDetection:
mode: enabled
ignore:
- paths: ["/spec/replicas"]
```

There's much more in the upcoming Flux v2.2.0 release, more updates and improvements for all of Flux's controllers, and a major overhaul of the dependencies from the perspective of image-automation-controller!

(Stay tuned for more details in a future post!)

If you need help with anything or have feedback, we've got a Slack channel, GitHub discussions, and many other ways to get help from the Flux maintainers, contributors, and community: [fluxcd.io/support/](https://fluxcd.io/support/)