-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
Installer Sprint 278
-
None
-
None
-
None
The installer is currently blocked from updating critical dependencies such as openshift/api and individual cluster-api providers. The issue is due to a pair of breaking changes in k8s.io/apimachinery v0.33 and sigs.k8s.io/cluster-api v1.11.
Cluster API v1.11 introduced significant breaking changes by relocating the APIs into subpackages (such a change should have warranted a module version bump, which would have avoided this problem for us). This means that in order to bump to CAPI v1.11, we will need to bump all providers simultaneously.
openshift/api depends on k8s.io/apimachinery v0.33, but bumping that breaks CAPI v1.10 (I don't have the error handy). So we are blocked from updating openshift/api until we bump capi to v1.11 and therefore all of its providers.
Provider | CAPI Version | Notes |
---|---|---|
CAPA | v1.10 | https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/5687 |
CAPZ | v1.10 | https://github.com/kubernetes-sigs/cluster-api-provider-azure/pull/5661 |
CAPZASH | v1.10 | we can refactor to remove the dependency on this |
CAPG | v1.11 | main is on v1.11, but v1.11 is not in a release |
CAPIBM | v1.11 | release v0.12.0 |
CAPX | v1.10 | https://github.com/nutanix-cloud-native/cluster-api-provider-nutanix/pull/590 |
CAPO | v1.11 | release v0.13.0 |
CAPV | v1.14 | release v1.14.0 |