alexlebens/infrastructure
1
0
Fork 0
Code Issues 1 Pull Requests 2 Actions Activity

chore(deps): update dependency mariadb-operator/mariadb-operator to v25.10.4 - autoclosed #3412

Closed
renovate-bot wants to merge 1 commits from renovate/mariadb-operator-mariadb-operator-25.x into main
pull from: renovate/mariadb-operator-mariadb-operator-25.x
merge into: alexlebens:main
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate-bot commented 2026-01-23 20:59:57 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
mariadb-operator/mariadb-operator patch 25.10.2 → 25.10.4

⚠️ Warning

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

Release Notes

mariadb-operator/mariadb-operator (mariadb-operator/mariadb-operator)

v25.10.4

Compare Source

mariadb-operator 25.10.4 is here! 🦭

This patch release includes several bug fixes and minor enhancements for the 25.10.x series, see the changelog below for details.

mariadb-cluster changes in values

The cluster helm chart facilitates the installation of multiple MariaDB instances in the same namespace. For doing so, by using the default values, the release name will used to prefix the generated Secrets, including the
root password which is now generated by default. Make sure you explicitly set mariadb.rootPasswordSecretKeyRef.generate=false to be backwards compatible.

See #​1572 for additional details.

Roadmap

We are excited to share the roadmap for the upcoming releases:

Community

Contributions of any kind are always welcome: adding yourself to the list of adopters, reporting issues, submitting pull requests, or simply starring the project! 🌟

Enterprise

For enterprise users, see the MariaDB Enterprise Operator, a commercially supported Kubernetes operator from MariaDB with additional enterprise-grade features.

What's Changed

New Contributors

Full Changelog: https://github.com/mariadb-operator/mariadb-operator/compare/25.10.3...25.10.4

v25.10.3

Compare Source

mariadb-operator 25.10.3 is here! 🦭

The focus of this release has been improving our backup and restore capabilities, along with various bug fixes and enhancements.

We are also announcing support for Kubernetes 1.35 and our roadmap for upcoming releases.

PhysicalBackup target policy

You are now able to define a target for PhysicalBackup resources, allowing you to control in which Pod the backups will be scheduled:

apiVersion: k8s.mariadb.com/v1alpha1
kind: PhysicalBackup
metadata:
  name: physicalbackup
spec:
  mariaDbRef:
    name: mariadb
  target: Replica

By default, the Replica policy is used, meaning that backups will only be scheduled on ready replicas. Alternatively, you can use the PreferReplica policy to schedule backups on replicas when available, or fall back to the primary if no replicas are available.

This is particularly useful in scenarios where you have a limited number of replicas, for instance, a primary-replica topology (single primary, single replica). By using the PreferReplica policy in this scenario, not only you ensure that backups are taken even if there are no available replicas, but also enables replica recovery operations, as they rely on PhysicalBackup resources successfully completing:

apiVersion: k8s.mariadb.com/v1alpha1
kind: MariaDB
metadata:
  name: mariadb-repl
spec:
  rootPasswordSecretKeyRef:
    name: mariadb
    key: root-password
  storage:
    size: 10Gi
  replicas: 2
  replication:
    enabled: true
    replica:
      bootstrapFrom:
        physicalBackupTemplateRef:
          name: physicalbackup-tpl
      recovery:
        enabled: true
---
apiVersion: k8s.mariadb.com/v1alpha1
kind: PhysicalBackup
metadata:
  name: physicalbackup-tpl
spec:
  mariaDbRef:
    name: mariadb-repl
    waitForIt: false
  schedule:
    suspend: true
  target: PreferReplica
  storage:
    s3:
      bucket: physicalbackups
      prefix: mariadb
      endpoint: minio.minio.svc.cluster.local:9000
      region:  us-east-1
      accessKeyIdSecretKeyRef:
        name: minio
        key: access-key-id
      secretAccessKeySecretKeyRef:
        name: minio
        key: secret-access-key
      tls:
        enabled: true
        caSecretKeyRef:
          name: minio-ca
          key: ca.crt

In the example above, a MariaDB primary-replica cluster is defined with the ability to recover and rebuild the replica from a PhysicalBackup taken on the primary, thanks to the PreferReplica target policy.

For additional details, please refer to the PhysicalBackup documentation and the replica recovery section.

Backup encryption

Logical and physical backups i.e. Backup and PhysicalBackup resources have gained support for encrypting backups on the server-side when using S3 storage. For doing so, you need to generate an encryption key and configure the backup resource to use it:

apiVersion: v1
kind: Secret
type: Opaque
metadata:
  name: ssec-key
stringData:
  # 32-byte key encoded in base64 (use: openssl rand -base64 32)
  customer-key: YWJjZGVmZ2hpamtsbW5vcHFyc3R1dnd4eXoxMjM0NTY=
---
apiVersion: k8s.mariadb.com/v1alpha1
kind: PhysicalBackup
metadata:
  name: physicalbackup
spec:
  mariaDbRef:
    name: mariadb
  storage:
    s3:
      bucket: physicalbackups
      endpoint: minio.minio.svc.cluster.local:9000
      accessKeyIdSecretKeyRef:
        name: minio
        key: access-key-id
      secretAccessKeySecretKeyRef:
        name: minio
        key: secret-access-key
      tls:
        enabled: true
        caSecretKeyRef:
          name: minio-ca
          key: ca.crt
      ssec:
        customerKeySecretKeyRef:
          name: ssec-key
          key: customer-key

In order to boostrap a new instance from an encrypted backup, you need to provide the same encryption key in the MariaDB bootstrapFrom section.

Kudos to @​xavierleune for this initiative and the PR contributing this feature! 🎉

Deprecating embedded MaxScale

To improve maintainability, minimize complexity and reduce the size of the CRD bundle (getting close to the 1MB hard limit), we are deprecating the MaxScale embedded definition inside the MariaDB CR in favor of deploying MaxScale as a separate CR.

To make the transition easier, we are providing you with this migration script. Refer to the MaxScale documentation for additional details.

Roadmap

We are very excited to share the roadmap for the upcoming releases:

  • Point In Time Recovery (PITR): You have been requesting this for a while, and it is completely aligned with our roadmap. We are actively working on this and we expect to release it on early 2026.
  • Multi-cluster topology: We are working on a new highly available topology that will allow you to setup replication between 2 different MariaDB clusters, allowing you to perform promotion and demotion of the clusters declaratively.

Community

Contributions of any kind are always welcome: adding yourself to the list of adopters, reporting issues, submitting pull requests, or simply starring the project! 🌟

Enterprise

For enterprise users, see the MariaDB Enterprise Operator, a commercially supported Kubernetes operator from MariaDB with additional enterprise-grade features.

What's Changed

New Contributors

Full Changelog: https://github.com/mariadb-operator/mariadb-operator/compare/25.10.2...25.10.3

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 PR is behind base branch, or you tick the rebase/retry checkbox.

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

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

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [mariadb-operator/mariadb-operator](https://github.com/mariadb-operator/mariadb-operator) | patch | `25.10.2` → `25.10.4` | --- > ⚠️ **Warning** > > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>mariadb-operator/mariadb-operator (mariadb-operator/mariadb-operator)</summary> ### [`v25.10.4`](https://github.com/mariadb-operator/mariadb-operator/releases/tag/25.10.4) [Compare Source](https://github.com/mariadb-operator/mariadb-operator/compare/25.10.3...25.10.4) **`mariadb-operator` [25.10.4](https://github.com/mariadb-operator/mariadb-operator/releases/tag/25.10.4) is here!** 🦭 This patch release includes several bug fixes and minor enhancements for the 25.10.x series, see the changelog below for details. #### `mariadb-cluster` changes in values The cluster helm chart facilitates the installation of multiple `MariaDB` instances in the same namespace. For doing so, by using the default values, the release name will used to prefix the generated `Secrets`, including the root password which is now generated by default. Make sure you explicitly set `mariadb.rootPasswordSecretKeyRef.generate=false` to be backwards compatible. See [#&#8203;1572](https://github.com/mariadb-operator/mariadb-operator/pull/1572) for additional details. #### Roadmap We are excited to share the roadmap for the upcoming releases: - [ ] [Point In Time Recovery (PITR)](https://github.com/mariadb-operator/mariadb-operator/issues/507) - [ ] [Multi-cluster topology](https://github.com/mariadb-operator/mariadb-operator/issues/1543) *** #### Community Contributions of any kind are always welcome: adding yourself to the [list of adopters](https://github.com/mariadb-operator/mariadb-operator/blob/main/ADOPTERS.md), reporting issues, submitting pull requests, or simply starring the project! 🌟 #### Enterprise For enterprise users, see the **[MariaDB Enterprise Operator](https://mariadb.com/products/enterprise/kubernetes-operator/)**, a commercially supported Kubernetes operator from MariaDB with additional enterprise-grade features. #### What's Changed - fix: \[Bug] args field on backup/restore resources lead to duplicate args on generated job resources by [@&#8203;majiayu000](https://github.com/majiayu000) in [#&#8203;1546](https://github.com/mariadb-operator/mariadb-operator/pull/1546) - Bump github.com/kubernetes-csi/external-snapshotter/client/v8 from 8.2.0 to 8.4.0 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;1547](https://github.com/mariadb-operator/mariadb-operator/pull/1547) - Bump golang.org/x/sync from 0.18.0 to 0.19.0 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;1548](https://github.com/mariadb-operator/mariadb-operator/pull/1548) - Bump go.uber.org/zap from 1.27.0 to 1.27.1 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;1549](https://github.com/mariadb-operator/mariadb-operator/pull/1549) - Bump github.com/gruntwork-io/terratest from 0.52.0 to 0.54.0 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;1550](https://github.com/mariadb-operator/mariadb-operator/pull/1550) - Bump github.com/hashicorp/go-version from 1.7.0 to 1.8.0 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;1551](https://github.com/mariadb-operator/mariadb-operator/pull/1551) - Remove embedded MaxScale leftovers by [@&#8203;mmontes11](https://github.com/mmontes11) in [#&#8203;1552](https://github.com/mariadb-operator/mariadb-operator/pull/1552) - docs: add documentation for Connection resources by [@&#8203;majiayu000](https://github.com/majiayu000) in [#&#8203;1555](https://github.com/mariadb-operator/mariadb-operator/pull/1555) - feat(storage): add pvcRetentionPolicy field to configure PVC retention by [@&#8203;majiayu000](https://github.com/majiayu000) in [#&#8203;1554](https://github.com/mariadb-operator/mariadb-operator/pull/1554) - perf: http.Transport created now has same defaults as http.DefaultTransport by [@&#8203;Michaelpalacce](https://github.com/Michaelpalacce) in [#&#8203;1565](https://github.com/mariadb-operator/mariadb-operator/pull/1565) - make embed-entrypoint for 2025q4 by [@&#8203;grooverdan](https://github.com/grooverdan) in [#&#8203;1567](https://github.com/mariadb-operator/mariadb-operator/pull/1567) - Bump crate-ci/typos from 1.40.0 to 1.41.0 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;1564](https://github.com/mariadb-operator/mariadb-operator/pull/1564) - Bump github.com/minio/minio-go/v7 from 7.0.95 to 7.0.97 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;1563](https://github.com/mariadb-operator/mariadb-operator/pull/1563) - Bump github.com/spf13/cobra from 1.10.1 to 1.10.2 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;1562](https://github.com/mariadb-operator/mariadb-operator/pull/1562) - Bump github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring from 0.85.0 to 0.87.1 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;1561](https://github.com/mariadb-operator/mariadb-operator/pull/1561) - Fixing `PhysicalBackup` scheduling for Galera by [@&#8203;mmontes11](https://github.com/mmontes11) in [#&#8203;1570](https://github.com/mariadb-operator/mariadb-operator/pull/1570) - Bump github.com/onsi/gomega from 1.38.2 to 1.38.3 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;1560](https://github.com/mariadb-operator/mariadb-operator/pull/1560) - Bump github.com/onsi/ginkgo/v2 from 2.27.2 to 2.27.3 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;1559](https://github.com/mariadb-operator/mariadb-operator/pull/1559) - Improve secref handling in mariadb-cluster chart by [@&#8203;hedgieinsocks](https://github.com/hedgieinsocks) in [#&#8203;1572](https://github.com/mariadb-operator/mariadb-operator/pull/1572) - Release 25.10.4 by [@&#8203;mmontes11](https://github.com/mmontes11) in [#&#8203;1571](https://github.com/mariadb-operator/mariadb-operator/pull/1571) #### New Contributors - [@&#8203;majiayu000](https://github.com/majiayu000) made their first contribution in [#&#8203;1546](https://github.com/mariadb-operator/mariadb-operator/pull/1546) **Full Changelog**: <https://github.com/mariadb-operator/mariadb-operator/compare/25.10.3...25.10.4> ### [`v25.10.3`](https://github.com/mariadb-operator/mariadb-operator/releases/tag/25.10.3) [Compare Source](https://github.com/mariadb-operator/mariadb-operator/compare/25.10.2...25.10.3) **`mariadb-operator` [25.10.3](https://github.com/mariadb-operator/mariadb-operator/releases/tag/25.10.3) is here!** 🦭 The focus of this release has been improving our backup and restore capabilities, along with various bug fixes and enhancements. We are also announcing [support for Kubernetes 1.35](https://github.com/mariadb-operator/mariadb-operator/pull/1542/files) and our roadmap for upcoming releases. #### `PhysicalBackup` target policy You are now able to define a `target` for `PhysicalBackup` resources, allowing you to control in which `Pod` the backups will be scheduled: ```yaml apiVersion: k8s.mariadb.com/v1alpha1 kind: PhysicalBackup metadata: name: physicalbackup spec: mariaDbRef: name: mariadb target: Replica ``` By default, the `Replica` policy is used, meaning that backups will only be scheduled on ready replicas. Alternatively, you can use the `PreferReplica` policy to schedule backups on replicas when available, or fall back to the primary if no replicas are available. This is particularly useful in scenarios where you have a limited number of replicas, for instance, a primary-replica topology (single primary, single replica). By using the `PreferReplica` policy in this scenario, not only you ensure that backups are taken even if there are no available replicas, but also enables replica recovery operations, as they rely on `PhysicalBackup` resources successfully completing: ```yaml apiVersion: k8s.mariadb.com/v1alpha1 kind: MariaDB metadata: name: mariadb-repl spec: rootPasswordSecretKeyRef: name: mariadb key: root-password storage: size: 10Gi replicas: 2 replication: enabled: true replica: bootstrapFrom: physicalBackupTemplateRef: name: physicalbackup-tpl recovery: enabled: true --- apiVersion: k8s.mariadb.com/v1alpha1 kind: PhysicalBackup metadata: name: physicalbackup-tpl spec: mariaDbRef: name: mariadb-repl waitForIt: false schedule: suspend: true target: PreferReplica storage: s3: bucket: physicalbackups prefix: mariadb endpoint: minio.minio.svc.cluster.local:9000 region: us-east-1 accessKeyIdSecretKeyRef: name: minio key: access-key-id secretAccessKeySecretKeyRef: name: minio key: secret-access-key tls: enabled: true caSecretKeyRef: name: minio-ca key: ca.crt ``` In the example above, a `MariaDB` primary-replica cluster is defined with the ability to recover and rebuild the replica from a `PhysicalBackup` taken on the primary, thanks to the `PreferReplica` target policy. For additional details, please refer to the [`PhysicalBackup` documentation](https://github.com/mariadb-operator/mariadb-operator/blob/main/docs/physical_backup.md) and the [replica recovery section](https://github.com/mariadb-operator/mariadb-operator/blob/main/docs/replication.md#replica-recovery). #### Backup encryption Logical and physical backups i.e. `Backup` and `PhysicalBackup` resources have gained support for encrypting backups on the server-side when using S3 storage. For doing so, you need to generate an encryption key and configure the backup resource to use it: ```yaml apiVersion: v1 kind: Secret type: Opaque metadata: name: ssec-key stringData: # 32-byte key encoded in base64 (use: openssl rand -base64 32) customer-key: YWJjZGVmZ2hpamtsbW5vcHFyc3R1dnd4eXoxMjM0NTY= --- apiVersion: k8s.mariadb.com/v1alpha1 kind: PhysicalBackup metadata: name: physicalbackup spec: mariaDbRef: name: mariadb storage: s3: bucket: physicalbackups endpoint: minio.minio.svc.cluster.local:9000 accessKeyIdSecretKeyRef: name: minio key: access-key-id secretAccessKeySecretKeyRef: name: minio key: secret-access-key tls: enabled: true caSecretKeyRef: name: minio-ca key: ca.crt ssec: customerKeySecretKeyRef: name: ssec-key key: customer-key ``` In order to boostrap a new instance from an encrypted backup, you need to provide the same encryption key in the `MariaDB` `bootstrapFrom` section. Kudos to [@&#8203;xavierleune](https://github.com/xavierleune) for this initiative and the PR contributing this feature! 🎉 #### Deprecating embedded `MaxScale` To improve maintainability, minimize complexity and reduce the size of the CRD bundle (getting close to the [1MB hard limit](https://azure.github.io/azure-service-operator/design/adr-2023-02-helm-chart-size-limitations/#:~:text=Helm%20v3%20stores%20chart%20state,a%20maximum%20size%20of%201MB.)), we are deprecating the [`MaxScale` embedded definition inside the `MariaDB` CR](https://github.com/mariadb-operator/mariadb-operator/blob/v25.10.2/docs/maxscale.md#maxscale-embedded-in-mariadb) in favor of deploying `MaxScale` as a separate CR. To make the transition easier, we are providing you with this [migration script](https://raw.githubusercontent.com/mariadb-operator/mariadb-operator/main/hack/migrate_maxscale_to_resource.sh). Refer to the [MaxScale documentation](https://github.com/mariadb-operator/mariadb-operator/blob/main/docs/maxscale.md) for additional details. #### Roadmap We are very excited to share the roadmap for the upcoming releases: - [Point In Time Recovery (PITR)](https://github.com/mariadb-operator/mariadb-operator/issues/507): You have been requesting this for a while, and it is completely aligned with our roadmap. We are [actively working](https://github.com/mariadb-operator/mariadb-operator/pull/1517) on this and we expect to release it on early 2026. - [Multi-cluster topology](https://github.com/mariadb-operator/mariadb-operator/issues/1543): We are working on a new highly available topology that will allow you to setup replication between 2 different `MariaDB` clusters, allowing you to perform promotion and demotion of the clusters declaratively. *** #### Community Contributions of any kind are always welcome: adding yourself to the [list of adopters](https://github.com/mariadb-operator/mariadb-operator/blob/main/ADOPTERS.md), reporting issues, submitting pull requests, or simply starring the project! 🌟 #### Enterprise For enterprise users, see the **[MariaDB Enterprise Operator](https://mariadb.com/products/enterprise/kubernetes-operator/)**, a commercially supported Kubernetes operator from MariaDB with additional enterprise-grade features. #### What's Changed - Fix extraArgs values in mariadb-operator chart by [@&#8203;hedgieinsocks](https://github.com/hedgieinsocks) in [#&#8203;1522](https://github.com/mariadb-operator/mariadb-operator/pull/1522) - Add cacheSyncTimeout by [@&#8203;hedgieinsocks](https://github.com/hedgieinsocks) in [#&#8203;1521](https://github.com/mariadb-operator/mariadb-operator/pull/1521) - Backup & Restore: support for SSE-C by [@&#8203;xavierleune](https://github.com/xavierleune) in [#&#8203;1520](https://github.com/mariadb-operator/mariadb-operator/pull/1520) - Refactor S3 by [@&#8203;mmontes11](https://github.com/mmontes11) in [#&#8203;1525](https://github.com/mariadb-operator/mariadb-operator/pull/1525) - Document namespaceOverride for mariadb-cluster by [@&#8203;hedgieinsocks](https://github.com/hedgieinsocks) in [#&#8203;1527](https://github.com/mariadb-operator/mariadb-operator/pull/1527) - Decoupled compression from backups by [@&#8203;mmontes11](https://github.com/mmontes11) in [#&#8203;1528](https://github.com/mariadb-operator/mariadb-operator/pull/1528) - Allow ExternalMariadb calls without providing client cert by [@&#8203;snaax](https://github.com/snaax) in [#&#8203;1443](https://github.com/mariadb-operator/mariadb-operator/pull/1443) - Using Specific helm version for locally and github workflows by [@&#8203;Michaelpalacce](https://github.com/Michaelpalacce) in [#&#8203;1515](https://github.com/mariadb-operator/mariadb-operator/pull/1515) - Feature/remove maxscale from maraidb cr by [@&#8203;Michaelpalacce](https://github.com/Michaelpalacce) in [#&#8203;1540](https://github.com/mariadb-operator/mariadb-operator/pull/1540) - Multiple fixes for 25.10.3 by [@&#8203;mmontes11](https://github.com/mmontes11) in [#&#8203;1541](https://github.com/mariadb-operator/mariadb-operator/pull/1541) - Bump golang to 1.25.5 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;1534](https://github.com/mariadb-operator/mariadb-operator/pull/1534) - Bump kubernetes 1.35 by [@&#8203;mmontes11](https://github.com/mmontes11) in [#&#8203;1542](https://github.com/mariadb-operator/mariadb-operator/pull/1542) - Bump ghcr.io/devcontainers/features/docker-in-docker from 2.12.3 to 2.13.0 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;1537](https://github.com/mariadb-operator/mariadb-operator/pull/1537) - Bump crate-ci/typos from 1.36.2 to 1.40.0 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;1524](https://github.com/mariadb-operator/mariadb-operator/pull/1524) - Bump helm/chart-testing-action from 2.7.0 to 2.8.0 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;1512](https://github.com/mariadb-operator/mariadb-operator/pull/1512) - Bump github.com/gruntwork-io/terratest from 0.50.0 to 0.52.0 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;1500](https://github.com/mariadb-operator/mariadb-operator/pull/1500) - Bump golangci/golangci-lint-action from 8 to 9 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;1511](https://github.com/mariadb-operator/mariadb-operator/pull/1511) - Bump actions/checkout from 5 to 6 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;1518](https://github.com/mariadb-operator/mariadb-operator/pull/1518) - Release 25.10.3 by [@&#8203;mmontes11](https://github.com/mmontes11) in [#&#8203;1526](https://github.com/mariadb-operator/mariadb-operator/pull/1526) #### New Contributors - [@&#8203;xavierleune](https://github.com/xavierleune) made their first contribution in [#&#8203;1520](https://github.com/mariadb-operator/mariadb-operator/pull/1520) - [@&#8203;snaax](https://github.com/snaax) made their first contribution in [#&#8203;1443](https://github.com/mariadb-operator/mariadb-operator/pull/1443) **Full Changelog**: <https://github.com/mariadb-operator/mariadb-operator/compare/25.10.2...25.10.3> </details> --- ### 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 PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi42OS4yIiwidXBkYXRlZEluVmVyIjoiNDIuNjkuMiIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->
renovate-bot added 1 commit 2026-01-23 21:00:00 +00:00
chore(deps): update dependency mariadb-operator/mariadb-operator to v25.10.4
All checks were successful
lint-test-helm / lint-helm (pull_request) Successful in 2m39s
Details
ebeecf4748
renovate-bot force-pushed renovate/mariadb-operator-mariadb-operator-25.x from ebeecf4748 to c024edd570 2026-01-23 22:14:10 +00:00 Compare
renovate-bot force-pushed renovate/mariadb-operator-mariadb-operator-25.x from c024edd570 to 2879d06cf3 2026-01-23 22:47:39 +00:00 Compare
renovate-bot force-pushed renovate/mariadb-operator-mariadb-operator-25.x from 2879d06cf3 to 76d398781d 2026-01-23 23:03:05 +00:00 Compare
renovate-bot changed title from chore(deps): update dependency mariadb-operator/mariadb-operator to v25.10.4 to chore(deps): update dependency mariadb-operator/mariadb-operator to v25.10.4 - autoclosed 2026-01-23 23:16:49 +00:00
renovate-bot closed this pull request 2026-01-23 23:16:50 +00:00
All checks were successful
lint-test-helm / lint-helm (pull_request) Successful in 17s
Details
render-manifests-automerge / render-manifests-automerge (pull_request) Has been skipped
Details
render-manifests-merge / render-manifests-merge (pull_request) Has been skipped
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Renovate
Issue generated by Renovate.
 automerge
This PR will be automerged by Renovate.
 chart
Chart update generated by Renovate.
 image
Image update generated by Renovate.
 stale
PR or Issue that has not been updated recently.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gitea-bot renovate-bot alexlebens
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: alexlebens/infrastructure#3412
Delete Branch "renovate/mariadb-operator-mariadb-operator-25.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?