Update dependency k-orc/openstack-resource-controller to v2.2.0 (main)

Sylva Renovate botrequested to merge
renovate/main-k-orc-openstack-resource-controller-2.x into main

This MR contains the following updates:

Package Update Change
k-orc/openstack-resource-controller minor v2.1.0 -> v2.2.0

Release Notes

k-orc/openstack-resource-controller (k-orc/openstack-resource-controller)

v2.2.0

Compare Source

What's Changed

New controllers
  • Floating IP
  • Server Group
New features
  • The subnet controller gained support for updating subnets. The rest of the controllers will follow in the next releases.
  • Added ability to specify which project to create resources in, for all networking controllers.
Bug fixes
  • Add an optional dependency of subnet on router: a subnet will now wait for the referenced router to be available before proceeding with creation. Likewise, the router won't be deleted until all subnets that depend on it are themselves deleted (Fixes #​316).
  • Fix the import of images, where the status may not reflect the real status of the resource.
  • Make the deletion of router interface more robust (Fixes #​378).
  • Add API validation to limit ExternalGateways to one until multiple gateways is effectively implemented in ORC (Fixes #​416).
  • Selectively stop populating status fields with zero values (Fixes #​188).
Update considerations

Although we don't guarantee that ORC runs fine on OpenStack versions that are no longer maintained by the OpenStack community, we've merged a change in this release that requires Nova from Stein. To the best of our knowledge, OpenStack Stein now becomes the minimum required version of OpenStack.

New Contributors

Full Changelog: https://github.com/k-orc/openstack-resource-controller/compare/v2.1.0...v2.2.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

  • If you want to rebase/retry this MR, check this box

This MR has been generated by Renovate Bot Sylva instance.

CI configuration couldn't be handle by MR description. A dedicated comment has been posted to control it.

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

Merge request reports