Skip to content

Flink Kubernetes Operator 1.16.0 - #877

Draft
Dennis-Mircea wants to merge 1 commit into
apache:asf-sitefrom
Dennis-Mircea:asf-site
Draft

Flink Kubernetes Operator 1.16.0#877
Dennis-Mircea wants to merge 1 commit into
apache:asf-sitefrom
Dennis-Mircea:asf-site

Conversation

@Dennis-Mircea

Copy link
Copy Markdown

No description provided.

Comment thread docs/content/posts/2026-08-06-release-kubernetes-operator-1.16.0.md Outdated
Comment thread docs/content/posts/2026-08-06-release-kubernetes-operator-1.16.0.md Outdated
Comment thread docs/content/posts/2026-08-06-release-kubernetes-operator-1.16.0.md Outdated
Comment thread docs/content/posts/2026-08-06-release-kubernetes-operator-1.16.0.md

@weiqingy weiqingy left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for putting this together. A few questions inline.


The Apache Flink community would like to thank all contributors who made this release possible:

Aleksandr Savonin, Attila Mészáros, Breno Ferreira, Dale Lane, Dennis-Mircea Ciupitu, Devika Sudheer, Farooq Qaiser, Gerk Elznik, Gyula Fora, Lucas Gameiro, lrsb, Marc Demierre, Milind L, Nihar Rao, Nishita Pattanayak, Pavel Zeger, Pradeepta Choudhury, Purushottam Sinha, Santwana Verma

@weiqingy weiqingy Aug 25, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I went through the commit range for this release and came up with 20 distinct authors, while this list has 19. The one I could not find here is Mate Czagany, who did f3f06136, the NOTICE fix for FLINK-40408 in #1182. Everyone else on the list matched up. Could they be added, or is there a reason they would not be in scope for this list?


The autoscaler becomes extensible through three new plugin SPIs, all discovered via the standard plugin mechanism and each configurable per named instance. Together they let you customize the autoscaler without forking it:

- **Custom Evaluator plugin ([FLIP-514](https://cwiki.apache.org/confluence/display/FLINK/FLIP-514)):** inject custom scaling-metric evaluation logic into the evaluation pipeline, augmenting or overriding how the autoscaler interprets the collected metrics before a scaling decision is made.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried these three links and they all come back 404. I think it is the shape of the URL rather than the FLIP numbers. Confluence wants the full page title in the path, and a known good one like FLIP-27 gives the same 404 in this form. The FLIPs themselves are all real and the descriptions here match their titles.

These full title versions work, if they are useful:

https://cwiki.apache.org/confluence/display/FLINK/FLIP-514%3A+Custom+Evaluator+plugin+for+Flink+Autoscaler
https://cwiki.apache.org/confluence/display/FLINK/FLIP-575%3A+Scaling+Executor+Plugin+SPI+for+Flink+Autoscaler
https://cwiki.apache.org/confluence/display/FLINK/FLIP-586%3A+Composable+Parallelism+Alignment+Modes+for+Flink+Autoscaler

The 2.3.0 release post links FLIPs with the short form instead (https://cwiki.apache.org/confluence/x/<id>), which reads a lot cleaner. Would that be worth matching here?

@@ -0,0 +1,131 @@
---
title: "Apache Flink Kubernetes Operator 1.16.0 Release Announcement"
date: "2026-08-06T08:00:00.000Z"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: the post is dated 2026-08-06, but rc2 was not tagged until 2026-08-21, so the date currently sits before the release candidate it describes. The same date is also in the filename, in the alias on line 8, and in release_date in docs/data/release_archive.yml. For 1.15 the release date landed after the tag (tagged May 7, released May 26). Is the plan to bump all four once the vote closes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants