Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Priority optional field is missing from CRD after is applied to k8s #531

Open
alita1991 opened this issue Apr 7, 2023 · 2 comments · May be fixed by #797
Open

Priority optional field is missing from CRD after is applied to k8s #531

alita1991 opened this issue Apr 7, 2023 · 2 comments · May be fixed by #797

Comments

@alita1991
Copy link

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.

@lsoica
Copy link

lsoica commented Apr 18, 2023

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?

@xpicio
Copy link

xpicio commented May 28, 2024

Hello, i have the same issue. At the moment i fixed with this configuration on Argo CD application:

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: apisix
  namespace: argo-cd
spec:
  ignoreDifferences:
    - group: apiextensions.k8s.io
      kind: CustomResourceDefinition
      jqPathExpressions:
        - '.spec.versions[].additionalPrinterColumns[]'

Now the sync process it's works 👋

@dezren39 dezren39 linked a pull request Jan 26, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants