We would like to share an upcoming change to our platforms infrastructure. To ensure we continue providing the most stable, secure, and modern GitOps environment, we are transitioning all legacy Flux API versions to their current General Availability (GA) versions.

What is changing?

As previously announced in our Central Update of Flux API Versions ,we have centrally managed the transition behind the scenes and updated all GitOps environment repositories to use the new Flux GA API standard. This change ensures that our systems remain robust, fully supported, and aligned with upstream technology lifecycles.

Why now?

Upcoming platform releases will fully retire and remove support for older, deprecated Flux API versions. By taking proactive action now, we ensure that your automated deployment pipelines remain uninterrupted and ready for future cluster updates.

What this means for you as our customer?

Although our teams have already successfully performed the bulk of the migration, **your team needs to take specific action** to maintain this state and prevent future deployment failures.

Strict requirements for future configurations:

• No Rollbacks: It is critical that your teams do not roll back any manifests or configurations to older, deprecated Flux API versions.
• No Legacy APIs in New Objects: Any newly added resources or objects must use the current GA versions. Do not introduce deprecated APIs into the repositories.

For reference, the following deprecated Flux API versions are no longer permitted and must not be used:

• `source.toolkit.fluxcd.io/v1beta1` and `source.toolkit.fluxcd.io/v1beta2`
• `kustomize.toolkit.fluxcd.io/v1beta1` and `kustomize.toolkit.fluxcd.io/v1beta2`
• `helm.toolkit.fluxcd.io/v2beta1` and `helm.toolkit.fluxcd.io/v2beta2`
• `notification.toolkit.fluxcd.io/v1beta1`
• `image.toolkit.fluxcd.io/v1beta1`

It is important that your development and platform teams cross-check all internal templates or CI/CD pipelines to ensure these legacy versions are no longer injected.

Expected Impact

Since our teams completed the updates centrally, no service interruptions or deployment downtime are expected. Please keep in mind, though, that if a deprecated API is accidentally re-introduced by your team, the respective GitOps reconciliation will fail.

Learn More

You can read more about the official upstream deprecation schedule and the technical background directly on GitHub:
Official Flux2 Tracking Issue: https://github.com/fluxcd/flux2/issues/5572

If you have any questions or require further alignment, please contact Intershop Support.