-
Notifications
You must be signed in to change notification settings - Fork 21
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
HMC
and velero
controller-runtime versions are incompatible
#794
Comments
Before any action can be taken for upstream, we should verify that bumping |
Related change by @zerospiel zerospiel/velero@5818629 |
Just to note: the aforementioned change is a kludge to make it work in the fork, nothing more, the actual implementation should contain generics |
Community page: https://velero.io/community/ |
Context
The
github.com/Mirantis/hmc
module currently hassigs.k8s.io/[email protected]
direct dependency along with thegithub.com/vmware-tanzu/[email protected]
, the latter utilizessigs.k8s.io/[email protected]
.Problem
These two versions of the CR have breaking changes hence importing any packages except API-related is not possible because the dependency tree cannot be resolved due to the aforementioned changes. To be precise the following are the errors produced during the
go build
of thehmc
binary:Resolution/DOD
The CR version in velero should be bumped at least to
0.19.0
(higher is better), and change the current implementation of the event handler here according to the updated interface in the CR.After bumping the minimal requirement, we have to bump
velero
module at least to the development branch, and waiting until a new tag has the updated CR version would be much better.The text was updated successfully, but these errors were encountered: