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 #536

Closed
kyle-google opened this issue Apr 19, 2024 · 3 comments
Closed

CustomResourceDefinition too long #536

kyle-google opened this issue Apr 19, 2024 · 3 comments

Comments

@kyle-google
Copy link

When applying a manifest during an upgrade you run into the following issue:

The CustomResourceDefinition "jobsets.jobset.x-k8s.io" is invalid: metadata.annotations: Too long: must have at most 262144 bytes

Current version: v0.3.2
Target Upgrade version: v0.5.0

@ahg-g
Copy link
Contributor

ahg-g commented Apr 19, 2024

are you using server side apply when installing it as described in https://jobset.sigs.k8s.io/docs/installation/#install-a-released-version?

@googs1025
Copy link
Member

You can install jobset using server-side mode
refer to: https://jobset.sigs.k8s.io/docs/installation/#install-a-released-version

kubectl apply --server-side -k github.com/kubernetes-sigs/jobset/config/default?ref=main

@kyle-google
Copy link
Author

Seeing an issue when trying to run this with dry-run on every resource:
Running command:

kubectl apply --dry-run=server --server-side -k PATH_TO_KUSTOMIZE

Example output:

Warning: failed to migrate kubectl.kubernetes.io/last-applied-configuration for Server-Side Apply. This is non-fatal and will be retried next time you apply. Error: Apply failed with 1 conflict: conflict with "kubectl-client-side-apply" using v1: .metadata.annotations.kubectl.kubernetes.io/last-applied-configuration

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

No branches or pull requests

4 participants