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

CustomResourceDefinition.apiextensions.k8s.io "prometheuses.monitoring.coreos.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes #57

Closed
megian opened this issue Oct 11, 2022 · 1 comment · Fixed by #58
Labels
bug Something isn't working

Comments

@megian
Copy link
Contributor

megian commented Oct 11, 2022

Deploying the Prometheus CRD seems to be too big to apply.

The apply work if it's done via server side apply together with --force-conflicts:

The CustomResourceDefinition "prometheuses.monitoring.coreos.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes
kubectl apply -f 10_prometheusOperator_0prometheusCustomResourceDefinition.yaml --server-side --force-conflicts

Size:

-rw-r--r-- 1 user user 523K Oct 10 17:37 10_prometheusOperator_0prometheusCustomResourceDefinition.yaml

Steps to Reproduce the Problem

  1. Use Kubernetes 1.23
  2. Compile the cluster catalog
  3. Apply with ArgoCD v2.3.4

Actual Behavior

Can't be applied because of the size

Expected Behavior

Apply does work regular with ArgoCD

@megian megian added the bug Something isn't working label Oct 11, 2022
@megian
Copy link
Contributor Author

megian commented Oct 11, 2022

Replacing the CRD with ArgoCD sync options:
vmeta42/metashow@1cf4f03

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant