Update dependency k-orc/openstack-resource-controller to v2.4.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.3.0 -> v2.4.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.4.0

Compare Source

What's Changed

New controllers
  • Keypair: Manage Nova SSH keypairs
  • Domain: Manage Keystone identity domains
  • Group: Manage Keystone identity groups
  • Role: Manage Keystone identity roles
  • Service: Manage Keystone identity services
New features
  • Server: Added ability to specify SSH keypair
  • Volume: Added support for availability zone
Bug fixes
  • Allow to use application credentials with access rules (Fixes #​596)
  • Fix actuator errors going silently (Fixes #​587)
  • Improve error message when cloud credentials can't be found in secret (Fixes #​589)
Infrastructure improvements
  • Go: Bumped to version 1.24.11
  • Bumped dependencies, most notably k8s libs to v0.34, controller-runtime to v0.22.4, and gophercloud to v2.9.0.
  • Added timeout environment variable for kuttl tests
  • Logging: Added log levels to more messages
  • Documentation: Major improvements to user and developer docs

New Contributors

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