You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/08/11 13:04:00 UTC

[jira] [Updated] (FLINK-37193) [flink-operator] Ingress recreated after perform a change to CR FlinkDeployment

     [ https://issues.apache.org/jira/browse/FLINK-37193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-37193:
-----------------------------------
    Labels: pull-request-available  (was: )

> [flink-operator] Ingress recreated after perform a change to CR FlinkDeployment
> -------------------------------------------------------------------------------
>
>                 Key: FLINK-37193
>                 URL: https://issues.apache.org/jira/browse/FLINK-37193
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Luís Costa
>            Assignee: Attila Mészáros
>            Priority: Minor
>              Labels: pull-request-available
>
> Greetings team,
> I'm using flink-operator v1.8.0.
> After performed somes changes on CR FlinkDeployment for my deployment, which was already created (change taskmanager replicas, add labels to pods) and the ingress is always recreated. Is it possible to make the ingress Immutable when no changes are done at ingress spec level? [~davidrad]
> Thanks in advance
> Best regards,
> Luís Costa



--
This message was sent by Atlassian Jira
(v8.20.10#820010)