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.

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

Prepare for Flux v2.3.0 #4712

Closed
58 of 59 tasks
Tracked by #45
stefanprodan opened this issue Apr 9, 2024 · 3 comments
Closed
58 of 59 tasks
Tracked by #45

Prepare for Flux v2.3.0 #4712

stefanprodan opened this issue Apr 9, 2024 · 3 comments
Labels
umbrella-issue Umbrella issue for tracking progress of a larger effort

Comments

@stefanprodan
Copy link
Member

stefanprodan commented Apr 9, 2024

Flux 2.3.0 promotes the Helm APIs to GA and comes with new features, bug fixes and performance improvements.

📅 Target dates: 13-14 May

🚀 Roadmap milestone: https://fluxcd.io/roadmap/#v23-q2-2024

API promotion

  • HelmRelease helm.toolkit.fluxcd.io/v2 (v2beta2 deprecated)
  • HelmRepository source.toolkit.fluxcd.io/v1 (v1beta2 deprecated)
  • HelmChart source.toolkit.fluxcd.io/v1 (v1beta2 deprecated)
  • ImageUpdateAutomation image.toolkit.fluxcd.io/v1beta2 (v1beta1 deprecated)

Dependencies updates

  • Kubernetes 1.30
  • Go 1.22
  • Kustomize 5.4
  • Helm 3.14
  • Cosign 2.2

Release checklist

  • source-controller v1.3.0
  • kustomize-controller v1.3.0
  • notification-controller v1.3.0
  • helm-controller: v1.0.1
  • image-reflector-controller v0.32.0
  • image-automation-controller v0.38.0
  • flux-benchmark v2.3.0
  • flux2 v2.3.0
  • terraform-provider-flux v1.3.0

Documentation

  • Update docs to promoted APIs
  • Publish Flux release change log to GitHub & Slack
  • Publish v2.3 website

Conformance testing

Distribution Versions
Kubernetes KinD 1.28.9, 1.29.4, 1.30.0
OpenShift 4.15.0-okd
K3s 1.28.7, 1.29.2
Google Cloud 1.28.7-gke.1026000

TODO

@siegenthalerroger
Copy link

Are release candidates being considered for these minor versions? Considering some of the issues found on the previous minor release, this might be a possible improvement.

I'm happy to raise this in a discussion or on slack if that's preferable.

@stefanprodan
Copy link
Member Author

Are release candidates being considered for these minor versions?

Not with the current team of core maintainers. A release takes about 2 full days for 2-3 people. We just don't have enough people to do work full-time on Flux.

@siegenthalerroger
Copy link

Are release candidates being considered for these minor versions?

Not with the current team of core maintainers. A release takes about 2 full days for 2-3 people. We just don't have enough people to do work full-time on Flux.

That's very understandable :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
umbrella-issue Umbrella issue for tracking progress of a larger effort
Projects
None yet
Development

No branches or pull requests

2 participants