Helm install of operator fails, CustomResourceDefinition too long

[jonathon2nd]

Expected behaviour

Installation of operator

Actual behaviour

Installation fails

Steps to reproduce the behaviour

Install with monitoring.enabled and monitoring.serviceMonitor enabled

Environment

How are the pieces configured?

• Redis Operator version: redis-operator:3.2.3
• Kubernetes version: v1.24.4+rke2r1
• Kubernetes configuration used (eg: Is RBAC active?): Too vague

Installing with Argo, which just uses helm chart and values.

Logs

CustomResourceDefinition.apiextensions.k8s.io "redisfailovers.databases.spotahome.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes

[alexey-demyanov]

Confirm. Same if you are trying to kubectl it.

# kubectl apply -f crd.yaml 
The CustomResourceDefinition "redisfailovers.databases.spotahome.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes

[alexey-demyanov]

But kubectl create is working.

[jonathon2nd]

Is this something that can be fixed?

[sotberd]

You can use --server-side apply. https://argo-cd.readthedocs.io/en/latest/user-guide/sync-options/#server-side-apply

[jonathon2nd]

That did not work either

[sotberd]

ArgoCD version ?

[jonathon2nd]

v2.4.12

[jonathon2nd]

Was able to apply with kubectl.

Since the helm can not upgrade the crd anyway, how about having a value in helm to exclude it (and have that default)? Has to be manually managed anyway.

[sotberd]

If ` syncOptions:

• ServerSideApply=true didn't work you can try syncOptions:
• Replace=true `

[jonathon2nd]

That worked.

[sotberd]

Nice 👍

[sotberd]

Confirm. Same if you are trying to kubectl it.

# kubectl apply -f crd.yaml 
The CustomResourceDefinition "redisfailovers.databases.spotahome.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes

try with kubectl apply --server-side -f crd.yaml