Update dependency kubernetes-sigs/cluster-api-provider-openstack to v0.12.1 (main) (!3837) · Merge requests · Sylva-projects / sylva-core

Notes

💡 This MR does more than just upgrade CAPO: it also adds a new controller which CAPO now relies on: the OpenStack Resource Controller (a.k.a ORC). This MR introduces a kustomize-units kustomization and a unit for this new component.💡

This MR is related to #2058 (closed) (because it generally aligns CAPO to the latest version, relying on CAPI 1.9 libs -- but there isn't any notion of dependency with CAPI 1.9.x controllers/CRDs)

Renovate bot description 🤖

This MR contains the following updates:

Package	Update	Change
kubernetes-sigs/cluster-api-provider-openstack	minor	`v0.11.4` -> `v0.12.1`

Release Notes

kubernetes-sigs/cluster-api-provider-openstack (kubernetes-sigs/cluster-api-provider-openstack)

`v0.12.1`

Compare Source

Changes since v0.12.0

Requiring Go 1.23.4 was too aggressive, some projects which have CAPO in their go.mod weren't ready. A best practice is to use 1.23.0 which we did.

🌱 Changes

go.mod: stick to 1.23.0 (#2425)
data: use latest Flatcar stable from image-builder (#2420)

Thanks to all our contributors! 😊

`v0.12.0`

Compare Source

Changes since v0.11

⚠️ Breaking Changes

ORC was removed from CAPO and now lives here. This documentation section explains how it can be installed in a cluster.
v1alpha6 API was removed in https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/2358

✨ New Features

Reconcile pre-existing router by @simonostendorf in https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/2338
Support for additional controlplane and worker secgroup rules (#2353)

🐛 Bug Fixes

Stop printing InstanceState for OpenStackMachine (#2406)
Ensure that existing ports also have correct tags and trunks (#2394)
fix: create lbaas in specified subnet (#2339)
New IPAddressClaim.ObjectMeta.Labels nil map assign panic (#2352)
ci/devstack: host tuning (#2307)
Better checks before creating Floating IPs (#2261)
Requeue when waiting for a server to be deleted (#2254)
Drop caBundle from CRDs to support Kubernetes 1.31 (#2238)
Fix support for OpenStackMachine.Spec.SecurityGroups (#2237)
Fix conversion of v1alpha6 PortOpts (#2207)
port/cleanup: support old bastion port name (#2409)

🌱 Others

k8s deps to v1.31.x
CAPI to v1.9.x
controller-runtime to 0.19.x
golang 1.23.4
E2E: Collect console log from machines (#2368)
Conformance: Fix warnings (#2357)
E2E: Use CAPI production images and skip cert-manager pre-pull (#2295)
Add libvirt resource type for create_devstack.sh (#2262)

📖 Additionally, there have been 3 contributions to our documentation and book. (#2376, #2296, #2268)

Thanks to all our contributors! 😊

This MR was initially generated by Renovate Bot Sylva instance.

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	`capd`, `capo`, `capm3`
🚀	Bootstrap Provider	`kubeadm` (alias `kadm`), `rke2`
🐧	Node OS	`ubuntu`, `suse`
🛠️	Deployment Options	`light-deploy`, `dev-sources`, `ha`, `misc`
🎬	Pipeline Scenarios	Available scenario list and description

Global config for deployment pipelines

autorun pipelines
allow failure on pipelines

Notes:

Enabling autorun will make deployment pipelines to be run automatically without human interaction
Disabling allow failure will make deployment pipelines mandatory for pipeline success.
if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.

⚙️ If no checkbox is checked, a default pipeline will be enabled (capm3, or capo if capo label is set)

Edited Feb 19, 2025 by Thomas Morin

Update dependency kubernetes-sigs/cluster-api-provider-openstack to v0.12.1 (main)