Flink Kubernetes Operator 1.15.0

[gyfora]

No description provided.

[Dennis-Mircea]

I see here that no concrete example follows the : put at the end. I'd suggest the follwing:

Suggested change

	The active framework is selected at install time via the new `logging.framework` Helm value:
	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

[Dennis-Mircea]

I would say that this paragraph could be a bit improved as there are more to highlight here. Based on the #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.

Suggested change

	StatsD.
	### 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.