Re: Flink Kubernetes Operator: Why one Helm repo for each version?

2023-12-01 Thread Salva Alcántara
Ok, thanks for the clarification.

On Fri, Dec 1, 2023 at 2:05 PM Gyula Fóra  wrote:

> Hi!
>
> I already answered your question on slack :
>
>
> “The main reason is that this allows us to completely separate release
> resources etc. much easier for the release process
>
> But this could be improved in the future if there is a good proposal for
> the process”
>
> Please do not cross post questions between slack and ml immediately, it’s
> more respectful of the contributors’ time if you only ask in a single place
> at a time.
>
> Cheers
> Gyula
>
> On Fri, 1 Dec 2023 at 13:31, Salva Alcántara 
> wrote:
>
>> Hi! I'm curious why there is not a single repo URL for the Flink
>> Kubernetes Operator Helm Chart, but multiples ones, one for each version.
>> This forces users to add one repo for each version, like this (directly
>> from the docs):
>>
>> ```
>> helm repo add flink-operator-repo
>> https://downloads.apache.org/flink/flink-kubernetes-operator-
>> /
>> helm install flink-kubernetes-operator
>> flink-operator-repo/flink-kubernetes-operator
>> ```
>>
>> This is weird and different from what I'm used to where you add the
>> (version-less) repo once and then install whatever version you need from
>> it...
>>
>


Re: Flink Kubernetes Operator: Why one Helm repo for each version?

2023-12-01 Thread Gyula Fóra
Hi!

I already answered your question on slack :


“The main reason is that this allows us to completely separate release
resources etc. much easier for the release process

But this could be improved in the future if there is a good proposal for
the process”

Please do not cross post questions between slack and ml immediately, it’s
more respectful of the contributors’ time if you only ask in a single place
at a time.

Cheers
Gyula

On Fri, 1 Dec 2023 at 13:31, Salva Alcántara 
wrote:

> Hi! I'm curious why there is not a single repo URL for the Flink
> Kubernetes Operator Helm Chart, but multiples ones, one for each version.
> This forces users to add one repo for each version, like this (directly
> from the docs):
>
> ```
> helm repo add flink-operator-repo
> https://downloads.apache.org/flink/flink-kubernetes-operator-
> /
> helm install flink-kubernetes-operator
> flink-operator-repo/flink-kubernetes-operator
> ```
>
> This is weird and different from what I'm used to where you add the
> (version-less) repo once and then install whatever version you need from
> it...
>


Flink Kubernetes Operator: Why one Helm repo for each version?

2023-12-01 Thread Salva Alcántara
Hi! I'm curious why there is not a single repo URL for the Flink Kubernetes
Operator Helm Chart, but multiples ones, one for each version. This forces
users to add one repo for each version, like this (directly from the docs):

```
helm repo add flink-operator-repo
https://downloads.apache.org/flink/flink-kubernetes-operator-
/
helm install flink-kubernetes-operator
flink-operator-repo/flink-kubernetes-operator
```

This is weird and different from what I'm used to where you add the
(version-less) repo once and then install whatever version you need from
it...