During the process of applying the Apisix CRDs via kubectl, I discovered that the priority field was missing on the live manifest. This issue was brought to my attention by the ArgoCD sync process, which detected the absence of the priority field in the applied CRD.

The following CRDs are impacted by this issue:

• apisixroutes.apisix.apache.org
• apisixpluginconfigs.apisix.apache.org

I'm looking for a way to ensure that the desired manifest is equal to the applied manifest, otherwise, ArgoCD SYNC will fail.