Thank you Dennis! These are both pretty serious issues and we should block the release until we have good fixes. In the meantime we should continue the validation to see if any other issue comes up.
Once we have the fixes merged I will create a new RC, thank you! Gyula On Wed, Aug 26, 2026 at 10:29 AM Dennis-Mircea Ciupitu <[email protected]> wrote: > > -1 (non-binding) > > > I performed the following actions successfully: > > - `mvn clean verify` using OpenJDK 17 + Maven 3.9.14 > - `helm unittest helm/flink-kubernetes-operator --file > "tests/**/*_test.yaml”` command > - Built the Docker image and installed the operator within Helm > - Ran the examples on normal runs and on different combinations > > > However, while running the examples by checking the new features added as > part of this new release, I hit the following problems, which I consider to > be real blockers: > > > - The same problem that Mate Czagany mentioned. This problem is always > visible for Flink 2.0+ jobs, and the errors are becoming a real noise and a > false alarm for healthy jobs that are properly configured. Also, this one > has a real consequence as well: a partial runtime config is silently > cached, and each cache refresh burns some seconds of a reconcile thread in > the RestClusterClient retry loop. > - The autoscaler parallelism overrides break every redeploy after a > scaling, for deployments running on Flink versions lower than 2.0. Since > FLINK-39791, the operator boots with the standard YAML parser, so the > scaling realizer serializes `pipeline.jobvertex-parallelism-overrides` into > the CR in the standard flow format, which the legacy parser of 1.x jobs > cannot read. In-place rescaling keeps working, so the problem is seen after > the first spec upgrade or last-state restore, where the job fails at > submission with "Could not parse value ... Illegal quoting". Based on > this, I created FLINK-40474 [1] bug with the full analysis, and I’m > going to provide a PR for it today. > > > Best regards, > > Dennis > > > [1] https://issues.apache.org/jira/browse/FLINK-40474 > > > On Tue, Aug 25, 2026 at 2:52 PM Samrat Deb <[email protected]> wrote: > > > +1 (non-binding) > > > > - Built from source with JDK 17, mvn clean verify succeeds > > - Source matches tag release-1.16.0-rc2 > > - Verified SHA512 checksums and GPG signatures > > - LICENSE/NOTICE present, RAT passes, no binaries in source > > > > Bests, > > Samrat > > > > On Tue, Aug 25, 2026 at 3:00 PM Mate Czagany <[email protected]> wrote: > > > > > +1 (non-binding) > > > > > > - Verified signatures and checksums > > > - No binaries in the source release > > > - Helm chart version and appVersion match, 1.16.0 > > > - Image tag in Helm chart is correct, `d6f8e84` > > > - Successfully built from source with JDK 17 and Maven 3.8.6 > > > - Verified NOTICE files, all looks good > > > - Verified JIRA release notes > > > - Ran the basic example job with Flink 2.2, upgraded parallelism, cleaned > > > up job. > > > > > > However I saw that the feature introduced by FLINK-35746 [1] that > > observes > > > the Flink configuration via REST does not correctly work for Flink 2.x > > jobs > > > as one of the expected fields was removed, and the operator still uses > > 1.20 > > > client. I have opened a PR [2] to fix it. I'm not sure if it's release > > > blocking. It only causes the new feature to not work properly for Flink > > 2.x > > > jobs. > > > > > > Best regards, > > > Mate > > > > > > [1] https://issues.apache.org/jira/browse/FLINK-35746 > > > [2] https://github.com/apache/flink-kubernetes-operator/pull/1193 > > > > > > On Tue, Aug 25, 2026 at 8:00 AM Weiqing Yang <[email protected]> > > > wrote: > > > > > > > +1 (non-binding) > > > > > > > > - Verified SHA512 checksums and GPG signatures (source, helm chart, > > > > index.yaml) > > > > - Source matches tag release-1.16.0-rc2 (dotfiles and the release image > > > pin > > > > aside) > > > > - LICENSE/NOTICE present, RAT passes, no binaries in source > > > > - Built from source with JDK 17, mvn clean verify passes > > > > - Ran the JDBC and docs integration tests with -Dit.skip=false > > > > - Checked Maven staging (artifacts present, signatures verified on > > every > > > > jar and pom) > > > > - Helm chart version and appVersion are 1.16.0, image tag matches the > > rc2 > > > > commit > > > > - Reviewed web PR #877 (a few comments, non-blocking) > > > > > > > > I don't think either is release blocking: link [3] points at f4f4582, > > the > > > > pre-version-bump commit, so that image is still on 1.16-SNAPSHOT while > > > the > > > > chart correctly uses d6f8e84. And reflectasm 1.09 is bundled in the > > > shaded > > > > jar but missing from NOTICE, same as in 1.15.0. > > > > > > > > Best, > > > > Weiqing > > > > > > > > On Fri, Aug 21, 2026 at 9:21 AM Gyula Fóra <[email protected]> wrote: > > > > > > > > > Hi Everyone, > > > > > Please review and vote on the release candidate #2 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-rc2" [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-rc2/ > > > > > [2] > > > > > > > > https://repository.apache.org/content/repositories/orgapacheflink-1939/ > > > > > [3] ghcr.io/apache/flink-kubernetes-operator:f4f4582 > > > > > [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-rc2 > > > > > [7] https://github.com/apache/flink-web/pull/877 > > > > > [8] > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Kubernetes+Operator+Release > > > > > > > > > > > > > >
