title: “Apache Flink Kubernetes Operator 1.12.0 Release Announcement” date: “2025-06-03T18:00:00.000Z” authors:
The Apache Flink community is excited to announce the release of Flink Kubernetes Operator 1.12.0! The version brings a number of important fixes and improvements to both core and autoscaler modules.
We encourage you to download the release and share your experience with the community through the Flink mailing lists or JIRA! We're looking forward to your feedback!
This release places a strong emphasis on improving the visibility and transparency of errors across the entire Flink Kubernetes Operator stack. These improvements aim to significantly enhance the user experience by making error diagnosis and resolution faster and more intuitive.
Comprehensive Event Reporting: Events are now emitted across all critical stages of the job lifecycle-from controller errors within the operator itself, to failures during job startup, and even runtime exceptions within Flink jobs. This end-to-end observability ensures that users are promptly informed of any issues that occur.
Detailed Error Messages: The operator now captures and surfaces more granular error messages for deployment and reconciliation failures. These messages are visible in the custom resource status and help users understand and address problems more effectively.
Automatic Kubernetes Event Generation: Whenever a job enters the FAILED state or restarts unexpectedly, the operator emits corresponding Kubernetes events. These events can be consumed by external monitoring systems or used directly in kubectl to monitor job health.
Improved Operator Diagnostics: Controller-level errors, which were previously difficult to trace, are now clearly reported and contextualized with helpful messages, allowing users and developers to better trace the root cause of failures.
These improvements make the Flink Kubernetes Operator more robust, transparent, and easier to operate, especially in complex or large-scale production environments.
config.yaml Support: The operator adds compatibility with Flink's config.yaml format, ensuring seamless integration with the latest Flink configurations.ReconciliationException and did not reach the FINISHED state in the custom resource.savepointInfo, ensuring accurate tracking of savepoints during upgrades.The full release notes can be found here.
The source artifacts and helm chart are available on the Downloads page of the Flink website. You can easily try out the new features shipped in the official 1.12.0 release by adding the Helm chart to your own local registry:
$ helm repo add flink-kubernetes-operator-1.12.0 https://archive.apache.org/dist/flink/flink-kubernetes-operator-1.12.0/ $ helm install flink-kubernetes-operator flink-kubernetes-operator-1.12.0/flink-kubernetes-operator --set webhook.create=false
You can also find official Kubernetes Operator Docker images of the new version on Dockerhub.
For more details, check the updated documentation and the release notes. We encourage you to download the release and share your feedback with the community through the Flink mailing lists or JIRA.
Andrea, Daren, David Kornel, Eduardas Kazakas, Gyula Fora, Nick Caballero, Rodrigo, Santwana Verma, Thomas Weise, ctrlaltdilj, pchoudhury22, siddr