You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2025/08/15 12:45:00 UTC
[jira] [Closed] (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 ]
Gyula Fora closed FLINK-37193.
------------------------------
Fix Version/s: kubernetes-operator-1.13.0
Resolution: Fixed
merged to main bb58a0a0388fbb080e25cd91ba5b061c5d00966e
> [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
> Fix For: kubernetes-operator-1.13.0
>
>
> 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)