Document Properties
Technical Impact Summary: Zero Service Disruption
- No Redeployments: Running applications will not be restarted, rebuilt, or rescheduled.
- No Service Interruptions: Pods, traffic routing, and infrastructure components remain entirely unaffected.
- No Action Required: The entire transition within the GitOps repositories is handled centrally by Intershop. Note: If these Flux API versions are utilized in external or custom integrations outside the GitOps repositories, adjustments must be managed independently.
To ensure the continued stability, security, and performance of the platform, preparations are underway for a mandatory platform-wide upgrade of the Flux GitOps controllers.
As part of this preparation, the Flux resource API versions within all GitOps repositories must be updated to their latest stable versions. To minimize operational overhead across the board, this version update will be performed centrally by Intershop across all customer GitOps repositories.
Technical Scope: What is being done?
The apiVersion declarations, transitioning from older beta versions to the stable v1 or v2, for all Flux custom resources, such as HelmRelease, Kustomization, and GitRepository, will be automatically updated by Intershop directly within the respective GitOps repositories.
This step is strictly required to ensure compatibility with upcoming Flux releases. Because the modifications are limited to administrative apiVersion strings in the YAML manifests while leaving the actual application configurations (spec) completely untouched, Kubernetes processes this as a purely administrative update.
For detailed technical information on the deprecation of older APIs, please refer to the official release notes:
Schedule: When will this happen?
The automated repository updates will be rolled out according to the following schedule:
- Non-Production Environments: June 02, 2026
- Production Environments: June 09, 2026
Support and Inquiries
In the event of unexpected behavior, or if further clarification regarding this schedule and update is required, please contact Intershop Support.
Disclaimer
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Website, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.