[
https://issues.apache.org/jira/browse/FLINK-37179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17923412#comment-17923412
]
Luís Costa edited comment on FLINK-37179 at 2/4/25 1:38 PM:
------------------------------------------------------------
Hello [~davidrad]
Since these are simply generated files, can _priority: 0_ be removed from all
CRDs in the next release?
https://github.com/apache/flink-kubernetes-operator/pull/940
was (Author: JIRAUSER286937):
Hello [~davidrad]
Since these are simply generated files, can _priority: 0_ be removed from all
CRDs in the next release?
> [ArgoCD] App Out Of Sync after update to v1.7.0
> -----------------------------------------------
>
> Key: FLINK-37179
> URL: https://issues.apache.org/jira/browse/FLINK-37179
> Project: Flink
> Issue Type: Improvement
> Reporter: Luís Costa
> Priority: Minor
> Labels: pull-request-available
> Attachments: Screenshot 2025-01-20 at 15.03.31.png
>
>
> Greetings team
> I am using ArgoCD to deploy flink-operator helm chart.
> After update to v1.7.0, the application is always out of sync, trying to
> replace the CRDs because those contain _*priority: 0*_. Figure in attachment.
> https://github.com/apache/flink-kubernetes-operator/blob/main/helm/flink-kubernetes-operator/crds/flinkdeployments.flink.apache.org-v1.yml#L20
> https://github.com/apache/flink-kubernetes-operator/blob/main/helm/flink-kubernetes-operator/crds/flinkdeployments.flink.apache.org-v1.yml#L26
> Instead of set it to 0, is this something that you can change to integer and
> make it optional for all CRDs? (or remove it if is not really needed)
> Thanks in advance
> Best regards,
> Luís Costa
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
