You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the problem/challenge you have #4382 complete velero migration from kubebuilder v2 to v3. After that, only apiextensions.k8s.io/v1 is supported, so there is no need to keep the --crds-version parameter to choose CRD version.
Describe the solution you'd like
Open this issue to trace removing the --crds-version parameter task.
Anything else you would like to add:
None
Environment:
Velero version (use velero version): v1.8
Kubernetes version (use kubectl version): 1.21
Kubernetes installer & version: kind
Cloud provider or hardware configuration: none
OS (e.g. from /etc/os-release): MacOS
Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
👍 for "The project would be better with this feature added"
👎 for "This feature will not enhance the project in a meaningful way"
The text was updated successfully, but these errors were encountered:
Describe the problem/challenge you have
#4382 complete velero migration from kubebuilder v2 to v3. After that, only apiextensions.k8s.io/v1 is supported, so there is no need to keep the --crds-version parameter to choose CRD version.
Describe the solution you'd like
Open this issue to trace removing the --crds-version parameter task.
Anything else you would like to add:
None
Environment:
velero version
): v1.8kubectl version
): 1.21/etc/os-release
): MacOSVote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
The text was updated successfully, but these errors were encountered: