You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Hit this as well. The problem is that for the default priority value of "0", it is stripped by the api server on get operations. Was the priority field with default value added for a specific reason?
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:
I'm looking for a way to ensure that the desired manifest is equal to the applied manifest, otherwise, ArgoCD SYNC will fail.
The text was updated successfully, but these errors were encountered: