Thanks Marton,
I vote for consistency and `flink-kubernetes-operator` as well.
`flink-operator` have been used widely in docker hub and other k8s operator
implementations, which may confuse users.
Best,
Biao
Gyula Fóra 于2022年3月30日周三 16:26写道：
> Thanks Marton!
> I think we should aim for
Thanks Marton!
I think we should aim for consistency and easy discoverability. Since we
use the name `flink-kubernetes-operator` for the project and everywhere on
the website to refer to it, I suggest adopting it as the name also.
This should be a very simple change that we can easily do before
Hi team,
I would like to ask for your input in naming the operator docker image and
helm chart. [1]
For the sake of brevity when we started the Kubernetes Operator work we
named the docker image and the helm chart simply flink-operator, while the
git repository is named
Hi Devs,
I am cancelling the current vote as we have promoted
https://issues.apache.org/jira/browse/FLINK-26916 as a blocker issue.
Yang has found a fix that we can reasonably do in a short time frame, so we
will work on that today before creating the next RC (hopefully later today)
Thank you!
Hi Devs,
I just want to give you heads up regarding a significant issue Matyas found
around the last-state upgrade mode:
https://issues.apache.org/jira/browse/FLINK-26916
Long story short, the last-state mode does not actually upgrade the job,
only the job/taskmanagers. The fix is non-trivial to
+1 non-binding, thanks for the great efforts and look forward to the
release!
Chenya
On Tue, Mar 29, 2022 at 2:10 AM Gyula Fóra wrote:
> Hi everyone,
>
> Please review and vote on the release candidate #2 for the version 0.1.0 of
> Apache Flink Kubernetes Operator,
> as follows:
> [ ] +1,
