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

remove --crds-version from "velero install" command #4389

Closed
blackpiglet opened this issue Nov 23, 2021 · 2 comments · Fixed by #4446
Closed

remove --crds-version from "velero install" command #4389

blackpiglet opened this issue Nov 23, 2021 · 2 comments · Fixed by #4446
Assignees
Milestone

Comments

@blackpiglet
Copy link
Contributor

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"
@reasonerjt
Copy link
Contributor

Please double check if this param is referenced in the doc and make sure it is removed also.

@blackpiglet
Copy link
Contributor Author

Please double check if this param is referenced in the doc and make sure it is removed also.

Got it. Checked the document. There is no recording of this parameter in documents.
Close this issue.

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

Successfully merging a pull request may close this issue.

2 participants