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

This MR contains the following updates:

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

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

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

v2.3.0

Compare Source

What's Changed

This release brings support for updating resources after creation for all relevant controllers. You can now modify your OpenStack infrastructure in-place without recreating resources, enabling true lifecycle management for production workloads.

It also adds support for the VolumeType and Volume controllers, completing the the core OpenStack resources coverage (compute, network, and storage).

New controllers
  • Volume: Manage Cinder block storage volumes
  • VolumeType: Manage Cinder volume types
New features
  • Added support for updating resources (mutability) for all relevant controllers
  • Server: Expose network interfaces status
  • Server: Added ability to attach and detach volumes and interfaces
  • Server: Added support for Availability Zone
  • Image: Added visibility filter support for image import
  • Added support for generating and publishing OLM bundle images
  • Added controller scaffolding tool for easier development
Bug fixes
  • Attachable resource now have their status more closely reflecting reality (Fixes #​282)
  • Documentation: Fixed examples in getting-started guide
  • Make ORC more suited for production environment by increasing memory limit to 256Mi and adjusing the API max items limits (Fixes #​527)
Infrastructure improvements
  • CI: Dropped caracal support, added epoxy and flamingo OpenStack versions
  • CI: Enabled openstack-cli-server for testing
  • Go: Bumped to version 1.24

New Contributors

Full Changelog: https://github.com/k-orc/openstack-resource-controller/compare/v2.2.0...v2.3.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

Loading