Hello, I've also noticed this in our Argo CD setup. Since priority=0 is the default, Kubernetes accepts it but doesn't store it in the actual resource, I'm guessing it's like a mutating admission hook that comes out of the box. The "priority" property can be safely removed from the CRDs.
Regards, Alexis. Am Do., 9. Mai 2024 um 22:03 Uhr schrieb Prasad, Neil < neil.pra...@activision.com>: > Sorry, let me explain. I currently have the operator deployed and managed > via ArgoCD. The CRDs I separated out into a different chart so I can do > upgrades on them. I am working on upgrading from version 1.7.0 to 1.8.0 > using ArgoCD. What I’ve done is replace the CRDs in the separate chart and > made sure ArgoCD runs a replace action against them. I then bumped the > chart version to 1.8.0 like so: > > dependencies: > > - name: flink-kubernetes-operator > > version: 1.8.0 > > repository: > https://downloads.apache.org/flink/flink-kubernetes-operator-1.8.0/ > > > > With those changes in place, ArgoCD still shows a diff specifically around > the additionalPrinterColumns section. The newer CRD versions have a line of > “priority: 0” under both Job Status and Lifecycle State but this is never > reflected in the cluster, either by replacing via ArgoCD or by hand. This > is the issue that I’m trying to resolve, how do I make sure this matches in > cluster when it doesn’t want to apply? Upgrading from 1.6.1 to 1.7.0 has > the same issue where that line (priority: 0) isn’t reflected. > > > > Now this doesn’t hurt the functionality we need but if we want to make > sure the CRDs are the same that are bundled in a release, then it’ll always > show a diff. > > > > *From: *Márton Balassi <balassi.mar...@gmail.com> > *Date: *Thursday, May 9, 2024 at 3:50 PM > *To: *Prasad, Neil <neil.pra...@activision.com> > *Cc: *user@flink.apache.org <user@flink.apache.org> > *Subject: *Re: Flink Kubernetes Operator 1.8.0 CRDs > > Hi, What do you mean exactly by cannot be applied or replaced? What > exactly is the issue? Are you installing fresh or trying to upgrade from a > previous version? If the latter please follow this: https: //nightlies. > apache. org/flink/flink-kubernetes-operator-docs-release-1. > 8/docs/operations/upgrade/#2-upgrading-the-crdOn > > > ZjQcmQRYFpfptBannerStart > > *This Message Is From an Untrusted Sender * > > You have not previously corresponded with this sender. > > > > ZjQcmQRYFpfptBannerEnd > > Hi, > > > > What do you mean exactly by cannot be applied or replaced? What exactly is > the issue? > > > > Are you installing fresh or trying to upgrade from a previous version? If > the latter please follow this: > > https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-release-1.8/docs/operations/upgrade/#2-upgrading-the-crd > <https://urldefense.com/v3/__https:/nightlies.apache.org/flink/flink-kubernetes-operator-docs-release-1.8/docs/operations/upgrade/*2-upgrading-the-crd__;Iw!!Ci6f514n9QsL8ck!j0sJH5o3E7AdaxqeUacWen27_56e_52lmHdH_ed8oHN1YuEZwzStZ_n403N78wZL3eW6ePLpG9giwfyEdtCYvilyHqBR$> > > > > On Thu, May 9, 2024 at 9:18 PM Prasad, Neil <neil.pra...@activision.com> > wrote: > > I am writing to report an issue with the Flink Kubernetes Operator version > 1.8.0. The CRD is unable to be applied or replaced in minikube or GKE. > However, the CRD works on version 1.7.0 of the operator. I thought it would > be helpful to bring this issue to the attention of the community and get > some help in case someone has run into this issue before . > > > > Thank you for your attention to this matter. > >
