Are there any other ways to transfer large CRD files?

[xiaoyu1095]

FILE="rayjobs.yaml"
GROUP_NAME="io.ray"
PACKAGE="io.ray"

docker run
--rm
-v pwd/src/main/resources/crd/${FILE}:pwd/src/main/resources/crd/${FILE}
-v /var/run/docker.sock:/var/run/docker.sock
-v /tmp/output:/tmp/output
-v "$(pwd)":"$(pwd)"
-ti
--network host
ghcr.io/kubernetes-client/java/crd-model-gen:v1.0.6
/generate.sh
-u pwd/src/main/resources/crd/${FILE}
-n ${GROUP_NAME}
-p ${PACKAGE}
-o "$(pwd)"

The CustomResourceDefinition "rayjobs.ray.io" is invalid: metadata.annotations: Too long: must have at most 262144 bytes
ps:
crd file : https://github.com/ray-project/kuberay/blob/master/ray-operator/config/crd/bases/ray.io_rayjobs.yaml

[brendandburns]

I think something is going wrong with the parsing here. I looked at your CRD, the annotations field isn't that long, I'm wondering if the YAML is messed up somehow.

[xiaoyu1095]

How is YAML transmitted? The file size is 1.2 MB, but Kubernetes label limits are usually 0.25 MB.

[brendandburns]

Ahh, I think that we must be using kubectl apply somewhere. That tries to shove the old object representation into an annotation (which then triggers this)

If we switch to kubectl create in that script it probably will work correctly. I don't think there's any reason to use apply

Any chance you can try making that change and seeing if it works?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten