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 too long error with latest Scylla Operator version #2157

Closed
susiesolis opened this issue Oct 16, 2024 · 1 comment · Fixed by #2170
Closed

CustomResourceDefinition too long error with latest Scylla Operator version #2157

susiesolis opened this issue Oct 16, 2024 · 1 comment · Fixed by #2170
Assignees
Labels
kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@susiesolis
Copy link
Contributor

What happened?

While following the Scylla Operator guide to deploy Scylla on Kubernetes, I encountered an error when applying the latest version of the Scylla Operator CRD file. The error message was as follows:

The CustomResourceDefinition "[scylladbdatacenters.scylla.scylladb.com](http://scylladbdatacenters.scylla.scylladb.com)" is invalid: metadata.annotations: Too long: must have at most 262144 bytes

Switching to version 1.12.1 of the Scylla Operator resolved the issue. It seems like the CRD file in the latest version exceeds a size limitation.

What did you expect to happen?

The Scylla Operator should have been deployed without encountering any size-related errors when applying the CRD file.

How can we reproduce it (as minimally and precisely as possible)?

Follow the Scylla Operator deployment guide.
Use the latest version of the Scylla Operator.

Run the command:

kubectl apply -f deploy/operator.yaml

Observe the error related to the CRD size being too long.

Scylla Operator version

Latest 1.14.1

Kubernetes platform name and version

$ kubectl version
kubectl version --client
Client Version: v1.31.1
Kustomize Version: v5.4.2

Kubernetes platform info:
Used an AWS ec2 instance with minikube

Please attach the must-gather archive.

N/A

Anything else we need to know?

No response

@susiesolis susiesolis added the kind/bug Categorizes issue or PR as related to a bug. label Oct 16, 2024
@scylla-operator-bot scylla-operator-bot bot added the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Oct 16, 2024
@tnozicka tnozicka added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Oct 16, 2024
@scylla-operator-bot scylla-operator-bot bot removed the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Oct 16, 2024
@tnozicka tnozicka added kind/documentation Categorizes issue or PR as related to documentation. and removed kind/bug Categorizes issue or PR as related to a bug. labels Oct 16, 2024
@swasik
Copy link

swasik commented Oct 17, 2024

I can confirm the issue - same problem in my case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants