changing the 'flink-main-container' name

[Nuno <fl...@gmail.com>]

Hello,

We just adopted the flink operator. According to this link
https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/
it prescribes a pod template containing among other things the following:

containers:    # Do not change the main container name    - name:
flink-main-container

I would actually like to change this name for each of my different
flink microservices, because having a bunch of microservices with the
same container name messes terribly with the container-based metrics
and dashboards of our monitoring system.

I'd like to try to understand if possible why this comment is there,
and how seriously should I take it ? What will break, concretely, if I
change it, please ?

I tried going through the operator code itself but couldn't find
anything concrete.

Any help to understand the underlying constraints will be very welcome.

Thank you very much!

Re: changing the 'flink-main-container' name

[Mate Czagany <cz...@gmail.com>]

Hi,

By naming the container flink-main-container, Flink will know which
container spec it should use for the Flink containers.
If you change the name Flink won't know which container spec to use for the
Flink container, and will probably think it's just a sidecar container, and
there will still be a flink-main-container with the default spec instead.

There is unfortunately no way to rename this container as of now.

Regards,
Mate

Nuno <fl...@gmail.com> ezt írta (időpont: 2023. okt. 20., P, 14:39):

> Hello,
>
> We just adopted the flink operator. According to this link
> https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/
> it prescribes a pod template containing among other things the following:
>
> containers:    # Do not change the main container name    - name: flink-main-container
>
> I would actually like to change this name for each of my different flink microservices, because having a bunch of microservices with the same container name messes terribly with the container-based metrics and dashboards of our monitoring system.
>
> I'd like to try to understand if possible why this comment is there, and how seriously should I take it ? What will break, concretely, if I change it, please ?
>
> I tried going through the operator code itself but couldn't find anything concrete.
>
> Any help to understand the underlying constraints will be very welcome.
>
> Thank you very much!
>
>