+1 (non-binding)
I performed the following actions successfully:
- Downloaded artifacts and verified signatures.
- Checked the POM file versions and NOTICE file diffs.
- Checked the release notes and re-validated them against the flink-web
PR.
- Ran `mvn clean verify` using OpenJDK 17 + Maven 3.9.14.
- Ran `helm unittest helm/flink-kubernetes-operator --file
"tests/**/*_test.yaml"` command.
- Built the Docker image and installed the operator via Helm.
- Ran the examples suite on Flink versions 1.20, 2.2, and 2.3
(latest), both on normal runs and on different combinations.
- Tested thoroughly the most important features of the current release
on both the operator examples and on custom, more complex pipelines:
- the new resource requirements support
- config.yaml replacement
- fetching of the runtime configuration
- autoscaler extensibility, enhancements, and hardening
2 things worth mentioning regarding signatures and NOTICE files:
- As @P Sinha <[email protected]> mentioned, a GPG signature
has expired.
- The com.esotericsoftware.reflectasm:reflectasm:1.09 dependency is
bundled in the shaded jar, but is not mentioned in the NOTICE file. For
this, I opened a PR [1]. Still, I see this change as non-trivial.
While testing, I discovered the following small items:
- FLINK-40535 [2] - Standalone session clusters are redeployed instead
of scaled in-place. (in-place since 1.6.0 operator version)
- FLINK-40581 [3] - Some examples were broken on the current Flink
version set. (minor)
- FLINK-40583 [4] - Operator keys are not filtered on some runtime
config paths. (minor to medium)
- FLINK-40587 [5] - Recreation of FlinkDeployment with a previous
autoscaler state throws an exception. (non-breaking, benign)
All of the above are already addressed as part of a different associated
PR. It is important to mention that all of the above are either minor or
not introduced by the current release, which doesn't represent a high
priority from my side, but they are still worth mentioning. I think we can
easily ship them in the next 1.17.0 operator release.
All the newly introduced features as part of the current release validate
successfully, and the release looks stable overall in my opinion, being the
main reason why I'd proceed with it in the current state.
Best,
Dennis
[1] https://github.com/apache/flink-kubernetes-operator/pull/1208
[2] https://issues.apache.org/jira/browse/FLINK-40535
[3] https://issues.apache.org/jira/browse/FLINK-40581
[4] https://issues.apache.org/jira/browse/FLINK-40586
[5] https://issues.apache.org/jira/browse/FLINK-40587
On Sat, Sep 5, 2026 at 12:48 PM P Sinha <[email protected]>
wrote:
> +1 (non-binding)
>
> - Verified SHA512 + GPG signatures (source, helm, index.yaml), key
> 21F06303B87DAFF1
> - Source matches tag release-1.16.0-rc3; LICENSE/NOTICE present, no
> binaries
> - Built from source with JDK 17, mvn clean verify passes (5642 unit tests,
> 0 failures)
> - Helm chart version/appVersion 1.16.0; image tag b395d61 matches the rc3
> commit
> and the image is on ghcr — the rc2 image-pin issue is resolved
> - Maven staging artifacts present with signatures on every jar and pom
> - FLINK-40465 (#1193) is included, fixing the Flink 2.x REST config issue
> from rc2
>
> One note (non-blocking): the signing key 21F06303B87DAFF1 shows as expired
> (2025-04-10) in
> dist/release/flink/KEYS while the signatures are dated 2026-08-27. Worth
> renewing the key and
> re-pushing KEYS.
>
> Best,
> Purushottam Sinha
>
> On Thu, Aug 27, 2026 at 8:05 PM Gyula Fóra <[email protected]> wrote:
>
> > Hi Everyone,
> > Please review and vote on the release candidate #3 for the version
> > 1.16.0 of Apache Flink Kubernetes Operator,
> > as follows:
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> > **Release Overview**
> >
> > As an overview, the release consists of the following:
> > a) Kubernetes Operator canonical source distribution (including the
> > Dockerfile), to be deployed to the release repository at
> > dist.apache.org
> > b) Kubernetes Operator Helm Chart to be deployed to the release
> > repository at dist.apache.org
> > c) Maven artifacts to be deployed to the Maven Central Repository
> > d) Docker image to be pushed to dockerhub
> >
> > **Staging Areas to Review**
> >
> > The staging areas containing the above mentioned artifacts are as
> > follows, for your review:
> > * All artifacts for a,b) can be found in the corresponding dev
> > repository at dist.apache.org [1]
> > * All artifacts for c) can be found at the Apache Nexus Repository [2]
> > * The docker image for d) is staged on github [3]
> >
> > All artifacts are signed with the key 21F06303B87DAFF1 [4]
> >
> > Other links for your review:
> > * JIRA release notes [5]
> > * source code tag "release-1.16.0-rc3" [6]
> > * PR to update the website Downloads page to include Kubernetes
> > Operator links [7]
> >
> > **Vote Duration**
> >
> > The voting time will run for at least 72 hours.
> > It is adopted by majority approval, with at least 3 PMC affirmative
> votes.
> >
> > **Note on Verification**
> >
> > You can follow the basic verification guide here[8].
> > Note that you don't need to verify everything yourself, but please
> > make note of what you have tested together with your +- vote.
> >
> > Cheers!
> > Gyula Fora
> >
> > [1]
> >
> https://dist.apache.org/repos/dist/dev/flink/flink-kubernetes-operator-1.16.0-rc3/
> > [2]
> > https://repository.apache.org/content/repositories/orgapacheflink-1942/
> > [3] ghcr.io/apache/flink-kubernetes-operator:b395d61
> > [4] https://dist.apache.org/repos/dist/release/flink/KEYS
> > [5]
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12356946
> > [6]
> >
> https://github.com/apache/flink-kubernetes-operator/tree/release-1.16.0-rc3
> > [7] https://github.com/apache/flink-web/pull/877
> > [8]
> >
> https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Kubernetes+Operator+Release
> >
>
>
> --
> Best Regards,
> Purushottam Sinha
> शुभकामनाएं
> पुरूषोत्तम सिन्हा
>
