Dennis-Mircea commented on code in PR #845: URL: https://github.com/apache/flink-web/pull/845#discussion_r3196026399
########## docs/content/posts/2026-05-04-release-kubernetes-operator-1.15.0.md: ########## @@ -0,0 +1,99 @@ +--- +title: "Apache Flink Kubernetes Operator 1.15.0 Release Announcement" +date: "2026-05-04T08:00:00.000Z" +authors: +- gyfora: + name: "Gyula Fora" +aliases: +- /news/2026/05/04/release-kubernetes-operator-1.15.0.html +--- + +The Apache Flink community is excited to announce the release of Flink Kubernetes Operator 1.15.0! + +This release brings **Kubernetes-native Conditions** to `FlinkDeployment`, **Logback logging support**, bundled metric reporters, Flink 2.2 compatibility, and a number of important reliability fixes across session jobs, savepoints, and the mutating webhook. + +We encourage you to [download the release](https://flink.apache.org/downloads.html) and share your experience with the +community through the Flink [mailing lists](https://flink.apache.org/community.html#mailing-lists) or +[JIRA](https://issues.apache.org/jira/browse/flink)! We're looking forward to your feedback! + +## Highlights + +### Kubernetes Conditions in FlinkDeployment Status + +The operator now exposes a standard Kubernetes +[Condition](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-conditions) in the `status` field of +`FlinkDeployment` resources. The `Running` condition gives tooling a consistent, machine-readable signal of whether +the deployment is up and running, directly usable with `kubectl wait`, GitOps controllers, and any tool that speaks +Kubernetes conditions. + +For example, to wait until a deployment is running: + +```shell +kubectl wait flinkdeployment/my-job --for=condition=Running --timeout=120s +``` + +### Logback Logging Support + +The operator now supports **Logback** as an alternative logging framework alongside the existing Log4j2 default. +The active framework is selected at install time via the new `logging.framework` Helm value: + +Both `logback-operator.xml` and `logback-console.xml` configuration files are bundled in the Helm chart and can be +customized the same way as the existing Log4j2 properties files. This is particularly useful for organizations that +standardize on Logback or rely on Logback-specific appenders and integrations. + +### Additional Metric Reporters Bundled + +The operator Helm chart now bundles several additional Flink metric reporter JARs out of the box, making it easier to +integrate with popular monitoring stacks without manual dependency management. The metrics documentation has also been +substantially expanded with detailed configuration examples covering common setups such as Prometheus, InfluxDB, and +StatsD. Review Comment: I would say that this paragraph could be a bit improved as there are more to highlight here. Based on the [#1102](https://github.com/apache/flink-kubernetes-operator/pull/1102) PR content only `flink-metrics-dropwizard` is bundled in this release (the OTel reporter is prepared but gated on Flink 2.0+), and Prometheus is the only reporter with a worked example in the new docs. ```suggestion ### Bundled Metric Reporters and Expanded Metrics Documentation The operator Helm chart now bundles the `flink-metrics-dropwizard` reporter out of the box, removing the need for users to add the JAR manually when integrating with monitoring stacks that consume Dropwizard metrics. The operator metrics documentation has also been substantially reworked: it now explains how operator-scoped metric identifiers are built, documents the `kubernetes.operator.metrics.*` prefix for operator-scoped reporter configuration, and walks through an end-to-end Prometheus monitoring setup. Most importantly, every metric the operator exposes is now documented in one place, with dedicated sections covering `FlinkDeployment` / `FlinkSessionJob` lifecycle and `JobStatus` tracking, `FlinkBlueGreenDeployment`, `FlinkStateSnapshot`, and autoscaler metrics, each with a clear explanation of what the metric measures and when it's emitted, so users finally have a complete picture of what's available out of the box. ``` ########## docs/content/posts/2026-05-04-release-kubernetes-operator-1.15.0.md: ########## @@ -0,0 +1,99 @@ +--- +title: "Apache Flink Kubernetes Operator 1.15.0 Release Announcement" +date: "2026-05-04T08:00:00.000Z" +authors: +- gyfora: + name: "Gyula Fora" +aliases: +- /news/2026/05/04/release-kubernetes-operator-1.15.0.html +--- + +The Apache Flink community is excited to announce the release of Flink Kubernetes Operator 1.15.0! + +This release brings **Kubernetes-native Conditions** to `FlinkDeployment`, **Logback logging support**, bundled metric reporters, Flink 2.2 compatibility, and a number of important reliability fixes across session jobs, savepoints, and the mutating webhook. + +We encourage you to [download the release](https://flink.apache.org/downloads.html) and share your experience with the +community through the Flink [mailing lists](https://flink.apache.org/community.html#mailing-lists) or +[JIRA](https://issues.apache.org/jira/browse/flink)! We're looking forward to your feedback! + +## Highlights + +### Kubernetes Conditions in FlinkDeployment Status + +The operator now exposes a standard Kubernetes +[Condition](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-conditions) in the `status` field of +`FlinkDeployment` resources. The `Running` condition gives tooling a consistent, machine-readable signal of whether +the deployment is up and running, directly usable with `kubectl wait`, GitOps controllers, and any tool that speaks +Kubernetes conditions. + +For example, to wait until a deployment is running: + +```shell +kubectl wait flinkdeployment/my-job --for=condition=Running --timeout=120s +``` + +### Logback Logging Support + +The operator now supports **Logback** as an alternative logging framework alongside the existing Log4j2 default. +The active framework is selected at install time via the new `logging.framework` Helm value: Review Comment: I see here that no concrete example follows the `:` put at the end. I'd suggest the follwing: ```suggestion The active framework is selected at install time via the new `logging.framework` Helm value: ```shell helm install flink-operator helm/flink-kubernetes-operator --set logging.framework=logback ``` ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
