Thanks all, I'm using other labels instead. Specifically, I'm using the
component label to select the pods I need for my networkpolicies.
- I agree that it would probably be best if flink k8s native did not use
this label.
- It would be nice if there was a common label applied to all pods
To clarify this logic is inherited from the Flink Native Kubernetes
integration itself. The operator specific labels we use are already fully
qualified.
I agree that this could be improved in Flink by a better label.
Cheers,
Gyula
On Thu, Jan 19, 2023 at 11:00 PM Mason Chen wrote:
> @Andrew I
@Andrew I was also confused by this earlier and FYI this line where it is
referenced
On a side note, we should probably use a qualified label name instead of
the pretty common app here. WDYT Gyula?
On Thu, Jan 19, 2023 at 1:48 PM Gyula Fóra wrote:
> Hi!
>
> The app label itself is used by Flink internally for a different purpose
> so it’s overriden. This is completely expected.
Hi!
The app label itself is used by Flink internally for a different purpose so
it’s overriden. This is completely expected.
I think it would be better to use some other label :)
Cheers,
Gyula
On Thu, 19 Jan 2023 at 19:02, Andrew Otto wrote:
> Hello!
>
> I'm seeing an unexpected label value
Hello!
I'm seeing an unexpected label value assignment happening, and I'm not sure
how it's happening. It is possible it is in my own helm charts and
templates somewhere, but I'm not seeing it, so I'm beginning to think this
is happening in the FlinkDeployment CRD in the operator code somewhere.
