Describe the solution you'd like
Velero is going to use kubebuilder v3 to generate operator code in v1.8, so migrating ServerStatusRequest that bases on kubebuilder v2 first.
Anything else you would like to add:
none
Environment:
Velero version (use velero version): v1.8
Kubernetes version (use kubectl version): v1.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.
:+1: for "The project would be better with this feature added"
:-1: for "This feature will not enhance the project in a meaningful way"
Describe the problem/challenge you have As an item of epic https://github.com/vmware-tanzu/velero/issues/4307, need to migrate ServerStatusRequest from kubebuilder v2 to v3.
Describe the solution you'd like Velero is going to use kubebuilder v3 to generate operator code in v1.8, so migrating ServerStatusRequest that bases on kubebuilder v2 first.
Anything else you would like to add: none
Environment:
velero version
): v1.8kubectl version
): v1.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.