Update dependency k-orc/openstack-resource-controller to v2.1.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.0.3 -> v2.1.0

Release Notes

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

v2.1.0

Compare Source

What's Changed

Release 2.1 marks the continuation of our efforts to stabilize and consolidate ORC.

We are now building multi-platform container images, supporting amd64, arm64, ppc64le and s390x platforms.

This release also brings initial support for Keystone resources in the form of the Project controller.

New controllers
  • Project
New features
  • ORC now passes the Kubernetes ReconcileID as the Request ID for all OpenStack API calls allowing to correlate the ORC and OpenStack logs, making troubleshooting much easier.
  • The image controller is now more consistent with other controllers.
  • Support setting new properties in the image controller: the hw_rng_model and hw_qemu_guest_agent hardware properties, and the os_distro, os_version, architecture and hypervisor_type properties.
  • The port controller now has the ability to set port security and vnic type.
Bug fixes
  • The user-agent header now includes the ORC versions, helping identify specific versions in logs for better support and debugging.
  • Add ability to create router interfaces for HA or DVR routers (Fixes #​330).
  • The status of servers is now reflected more accurately (Fixes #​280).

New Contributors

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