Re: [EXTERNAL]Re: Next Release of the Flink Kubernetes Operator

[Niklas Wilcke <ni...@uniberg.com>]

Hi Gyula,

thank you very much for the update about the release schedule and for pointing me to the snapshot images. This is indeed very helpful and we will consider our options now.

Regards,
Niklas

> On 16. Oct 2023, at 17:56, Gyula Fóra <gy...@gmail.com> wrote:
> 
> Hi Niklas!
> 
> We weren't planning a 1.6.1 release and instead we were focusing on wrapping up changes for the 1.7.0 release coming in a month or so.
> 
> However if there is enough interest and we have some committers/PMC willing to help with the release we can always do 1.6.1 but I personally don't have the bandwidth for it right now. 
> 
> In case you want to pick up the latest 1.6 backported fixes, you could either create a custom operator build or simply pick up the image built from the branch automatically [1]
> This would probably be an easy way to get the fixes into your environment. But of course this is not an official release, just a snapshot version so you have to do your own verification to make sure it works for you.
> 
> Cheers,
> Gyula
> 
> [1] https://github.com/apache/flink-kubernetes-operator/pkgs/container/flink-kubernetes-operator/127962962?tag=3f0dc2e
> 
> On Mon, Oct 16, 2023 at 5:41 PM Niklas Wilcke <niklas.wilcke@uniberg.com <ma...@uniberg.com>> wrote:
>> Hi Flink Community,
>> 
>> we are waiting for the next release of the Flink Kubernetes Operator, because we are experiencing problems with loosing the HA metadata similar to FLINK-33011 [0].
>> Since the problem is already fixed and also backported to the 1.6 branch [1], my question would be whether we can expect a release soon?
>> Any input is highly appreciated. Thank you!
>> 
>> Regards,
>> Niklas
>> 
>> 
>> [0] https://issues.apache.org/jira/browse/FLINK-33011
>> [1] https://github.com/apache/flink-kubernetes-operator/commits/release-1.6

Re: [EXTERNAL]Re: Next Release of the Flink Kubernetes Operator

[Gyula Fóra <gy...@gmail.com>]

Building your own custom operator image is also fairly straightforward and
is also a good exercise to make sure you can easily backport critical fixes
into your prod envs in the future :)

Cheers,
Gyula

On Tue, Oct 17, 2023 at 10:48 AM Niklas Wilcke <ni...@uniberg.com>
wrote:

> Hi Gyula,
>
> thank you very much for the update about the release schedule and for
> pointing me to the snapshot images. This is indeed very helpful and we will
> consider our options now.
>
> Regards,
> Niklas
>
> On 16. Oct 2023, at 17:56, Gyula Fóra <gy...@gmail.com> wrote:
>
> Hi Niklas!
>
> We weren't planning a 1.6.1 release and instead we were focusing on
> wrapping up changes for the 1.7.0 release coming in a month or so.
>
> However if there is enough interest and we have some committers/PMC
> willing to help with the release we can always do 1.6.1 but I personally
> don't have the bandwidth for it right now.
>
> In case you want to pick up the latest 1.6 backported fixes, you could
> either create a custom operator build or simply pick up the image built
> from the branch automatically [1]
> This would probably be an easy way to get the fixes into your environment.
> But of course this is not an official release, just a snapshot version so
> you have to do your own verification to make sure it works for you.
>
> Cheers,
> Gyula
>
> [1]
> https://github.com/apache/flink-kubernetes-operator/pkgs/container/flink-kubernetes-operator/127962962?tag=3f0dc2e
>
> On Mon, Oct 16, 2023 at 5:41 PM Niklas Wilcke <ni...@uniberg.com>
> wrote:
>
>> Hi Flink Community,
>>
>> we are waiting for the next release of the Flink Kubernetes Operator,
>> because we are experiencing problems with loosing the HA metadata similar
>> to FLINK-33011 [0].
>> Since the problem is already fixed and also backported to the 1.6 branch
>> [1], my question would be whether we can expect a release soon?
>> Any input is highly appreciated. Thank you!
>>
>> Regards,
>> Niklas
>>
>>
>> [0] https://issues.apache.org/jira/browse/FLINK-33011
>> [1]
>> https://github.com/apache/flink-kubernetes-operator/commits/release-1.6
>>
>
>