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

Issue with argo-cd upgrade #54

Closed
jonathon2nd opened this issue Dec 18, 2024 · 4 comments
Closed

Issue with argo-cd upgrade #54

jonathon2nd opened this issue Dec 18, 2024 · 4 comments

Comments

@jonathon2nd
Copy link

jonathon2nd commented Dec 18, 2024

Chart: snapshot-controller:4.0.0
Default values

Getting the following errors

apiextensions.k8s.io/v1/CustomResourceDefinition
linstor
volumegroupsnapshotclasses.groupsnapshot.storage.k8s.io
SyncFailed
CustomResourceDefinition.apiextensions.k8s.io "volumegroupsnapshotclasses.groupsnapshot.storage.k8s.io" is invalid: status.storedVersions[0]: Invalid value: "v1alpha1": must appear in spec.versions
apiextensions.k8s.io/v1/CustomResourceDefinition
linstor
volumegroupsnapshotcontents.groupsnapshot.storage.k8s.io
SyncFailed
CustomResourceDefinition.apiextensions.k8s.io "volumegroupsnapshotcontents.groupsnapshot.storage.k8s.io" is invalid: status.storedVersions[0]: Invalid value: "v1alpha1": must appear in spec.versions
apiextensions.k8s.io/v1/CustomResourceDefinition
linstor
volumegroupsnapshots.groupsnapshot.storage.k8s.io
SyncFailed
CustomResourceDefinition.apiextensions.k8s.io "volumegroupsnapshots.groupsnapshot.storage.k8s.io" is invalid: status.storedVersions[0]: Invalid value: "v1alpha1": must appear in spec.versions

Even when I attempt to replace and force
image

@WanzenBug
Copy link
Member

Looks like this is something done intentionally by the upstream project 🤦

This PR entirely removes the capability to serve the v1alpha version. Existing clients will be broken.
This is consistent with the kubernetes-csi/external-snapshotter#1150 (comment) and the related kubernetes-csi/external-snapshotter#1150 (comment).

@WanzenBug
Copy link
Member

Note: I closed this issue here, as this is not really the place to fix the issue. If there are any workarounds found, they can still be added here.

@jonathon2nd
Copy link
Author

@WanzenBug
Copy link
Member

I guess we could try to configure a pre-upgrade or pre-install hook for this 🤔

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

2 participants