cluster-api-provider-proxmox
cluster-api-provider-proxmox copied to clipboard
bump go to 1.22
Issue #, if available: fix #187
+mass dep update: k8s/api* to 0.30 controller-gen to 0.15.0 (0.14.0 has the go 1.22 panic fix) controller-runtime to 0.18.0 (dependency)
Regenerated crds using new controller-gen. Note config/rbac/role.yaml and config/webhook/manifest.yaml.
obsoletes #190
#177
I will squash this PR into a single commit because none of commits in the PR work without all the other commits in the PR.
@mcbenjemaa you need to be more specific - in what way are they not working?
sorry, my caches
We've decided against merging this until a cluster-api release with controller-runtime v0.18.0 support comes out.
None of the providers moved to 1.22 cause they follow capi:
- https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/go.mod
- https://github.com/kubernetes-sigs/cluster-api-provider-gcp/blob/main/go.mod
- https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/main/go.mod
- https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/main/go.mod
- https://github.com/kubernetes-sigs/cluster-api-provider-packet/blob/main/go.mod
- https://github.com/kubernetes-sigs/cluster-api-provider-ibmcloud/blob/main/go.mod
I recommend that we wait for the v1.8 release. To be compliant with CAPI.
capi 1.7.2 still does not support controller-runtime 0.18
Rebased for v0.5.0.
Quality Gate passed
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code
We can rework this now.
Ready for review.
e2e passed, pushing cosmetic changes to go.mod
Quality Gate passed
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code