This MR contains the following updates:

Package Update Change
https://gitlab.com/sylva-projects/sylva-elements/ci-tooling/ci-deployment-values.git patch 0.6.22 -> 0.6.24

⚠️ Warning

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


Release Notes

sylva-projects/sylva-elements/ci-tooling/ci-deployment-values (https://gitlab.com/sylva-projects/sylva-elements/ci-tooling/ci-deployment-values.git)

v0.6.24: ci-deployment-values: 0.6.24

Compare Source

Merge Requests integrated in this release

3 merge requests were integrated in this repo between 0.6.23 and 0.6.24. These notes don't account for the MRs merged in secondary repos.

Cluster API

  • increase replicas for capo maxsurge-0 scenario !465 capo

OpenStack capo

Other

  • backport 1.7: add values of sample-keycloak-users-groups-repo to ci values !498 backport

CI

  • Update dependency sylva-projects/sylva-elements/ci-tooling/ci-templates to v1.1.5 !499 renovate

Contributors

2 people contributed.

Samuel Bartel, Shreya Gupta

v0.6.23: ci-deployment-values: 0.6.23

Compare Source

Merge Requests integrated in this release

2 merge requests were integrated in this repo between 0.6.22 and 0.6.23. These notes don't account for the MRs merged in secondary repos.

OpenStack capo

OKD/OpenShift

CI

  • Update dependency sylva-projects/sylva-elements/ci-tooling/ci-templates to v1.1.4 !496 renovate
  • Add OKD on CAPO CI deployment values !448 capo okd

Contributors

1 person contributed.

Andrew Kiselev


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)

Edited by Sylva Renovate bot

Merge request reports

Loading
Loading