Hi Devs!
I'm happy to announce that we have unanimously approved this release.
There are 8 approving votes, 4 of which are binding:
* Gyula Fora (binding)
* Marton Balassi (binding)
* Thomas Weise (binding)
* Maximilian Michels (binding)
* Biao Geng (non-binding)
* Jim Busche (non-binding)
* Ma
Thank you everyone for testing, I am closing this vote.
Will post the results as a separate email.
Gyula
On Fri, Oct 7, 2022 at 5:38 AM Chenya Zhang wrote:
> +1 non-binding
>
> Tested a few example applications and checking the operator log.
>
> Chenya
>
> On Thu, Oct 6, 2022 at 3:18 PM Thomas
+1 non-binding
Tested a few example applications and checking the operator log.
Chenya
On Thu, Oct 6, 2022 at 3:18 PM Thomas Weise wrote:
> +1 (binding)
>
> Built from tag, manually tested upgrade mode change scenarios, upgraded
> existing environment
>
>
> On Thu, Oct 6, 2022 at 4:00 PM Márto
+1 (binding)
Built from tag, manually tested upgrade mode change scenarios, upgraded
existing environment
On Thu, Oct 6, 2022 at 4:00 PM Márton Balassi
wrote:
> +1 (binding)
>
> Verified upgrade process from 1.1 with a running application
>
> On Thu, Oct 6, 2022 at 5:52 PM Biao Geng wrote:
>
+1 (binding)
Verified upgrade process from 1.1 with a running application
On Thu, Oct 6, 2022 at 5:52 PM Biao Geng wrote:
> +1(non-binding)
> Thanks a lot for the great work.
>
> Successfully verified the following:
> - Checksums and gpg signatures of the tar files.
> - No binaries in source re
+1(non-binding)
Thanks a lot for the great work.
Successfully verified the following:
- Checksums and gpg signatures of the tar files.
- No binaries in source release
- Build from source, build image from source without errors
- Helm Repo works, Helm install works
- Run HA/python example in applic
Turns out the issue with the Helm installation was that I was using
cert-manager 1.9.1 instead of the recommended version 1.8.2. The operator
now deploys cleanly in my local environment.
On Thu, Oct 6, 2022 at 12:34 PM Maximilian Michels wrote:
> +1 (binding) because the source release looks goo
+1 (binding) because the source release looks good.
I've verified the following:
1. Downloaded, compiled, and verified the signature of the source release
staged at
https://dist.apache.org/repos/dist/dev/flink/flink-kubernetes-operator-1.2.0-rc2/
2. Verified licenses (Not a blocker: the LICENSE f
+1 (non-binding)
- Verified checksums
- Built and ran all the tests
- Verified all pom files point to the same version
- Verified helm chart works as expected and expected docker image
- Tested basic application clusters (v1.13-v1.15) on EKS 1.21.
On 05/10/2022, 13:16, "Őrhidi Mátyás" wrote:
+1 (non-binding)
- Verified source distributions (except the licenses and maven artifacts)
- Verified Helm chart and Docker image
- Verified basic examples
Everything seems okay to me.
Cheers,
Matyas
On Tue, Oct 4, 2022 at 10:27 PM Gyula Fóra wrote:
> +1 (binding)
>
> - Verified Helm repo wor
+1 (binding)
- Verified Helm repo works as expected, points to correct image tag, build,
version
- Verified examples + checked operator logs everything looks as expected
- Verified hashes, signatures and source release contains no binaries
- Ran built-in tests, built jars + docker image from sourc
+1 (not-binding)
Thank you Gyula,
Helm install from flink-kubernetes-operator-1.2.0-helm.tgz looks good, logs
look normal
podman Dockerfile build from source looks good.
twistlock security scans of the proposed image look good:
ghcr.io/apache/flink-kubernetes-operator:95128bf
UI and basic
Hi everyone,
Please review and vote on the release candidate #2 for the version 1.2.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 th
13 matches
Mail list logo
