chore(deps): update helm release mariadb-operator to v0.38.1 #363

renovate · 2023-10-11T19:57:25Z

This PR contains the following updates:

Package	Update	Change
mariadb-operator	minor	`0.20.0` -> `0.38.1`

Release Notes

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

`v0.38.1`

Compare Source

Run and operate MariaDB in a cloud native way

`v0.38.0`

Compare Source

Run and operate MariaDB in a cloud native way

`v0.37.1`

Compare Source

mariadb-operator 0.37.1 is here! 🦭

We're excited to introduce TLS 🔐 support in this release, one of the major features of mariadb-operator so far! ✨ Check out the TLS docs, our example catalog and the release notes below to start using it.

[!WARNING]
Be sure to follow the UPGRADE GUIDE to ensure a seamless transition from previous versions.

Issue certificates for `MariaDB` and `MaxScale`

Issuing and configuring TLS certificates for your instances has never been easier, you just need to set tls.enabled=true:

apiVersion: k8s.mariadb.com/v1alpha1
kind: MariaDB
metadata:
  name: mariadb-galera
spec:
  ...
  tls:
    enabled: true

apiVersion: k8s.mariadb.com/v1alpha1
kind: MaxScale
metadata:
  name: maxscale
spec:
  ...
  mariaDbRef:
    name: mariadb-galera
  tls:
    enabled: true

A self-signed Certificate Authority (CA) will be automatically generated to issue leaf certificates for your instances. The operator will also manage a CA bundle that your applications can use in order to establish trust.

TLS will be enabled by default in MariaDB, but it will not enforced. You can enforce TLS connections by setting tls.required=true to ensure that all connections are encrypted. In the case of MaxScale, TLS will only be enabled if you explicitly set tls.enabled=true or the referred MariaDB (via mariaDbRef) instance enforces TLS.

Native integration with cert-manager

cert-manager is the de facto standard for managing certificates in Kubernetes. This certificate controller simplifies the automatic provisioning, management, and renewal of certificates. It supports a variety of certificate backends (e.g. in-cluster, Hashicorp Vault), which are configured using Issuer or ClusterIssuer resources.

In your MariaDB and MaxScale resources, you can directly reference ClusterIssuer or Issuer objects to seamlessly issue certificates:

apiVersion: k8s.mariadb.com/v1alpha1
kind: MariaDB
metadata:
  name: mariadb-galera
spec:
  ...
  tls:
    enabled: true
    serverCertIssuerRef:
      name: root-ca
      kind: ClusterIssuer
    clientCertIssuerRef:
      name: root-ca
      kind: ClusterIssuer

apiVersion: k8s.mariadb.com/v1alpha1
kind: MaxScale
metadata:
  name: maxscale-galera
spec:
  ...
  tls:
    enabled: true
    adminCertIssuerRef:
      name: root-ca
      kind: ClusterIssuer
    listenerCertIssuerRef:
      name: root-ca
      kind: ClusterIssuer

Under the scenes, the operator will create cert-manager's Certificate resources with all the required Subject Alternative Names (SANs) required by your instances. These certificates will be automatically managed by cert-manager and the CA bundle will be updated by the operator so you can establish trust with your instances.

The advantage of this approach is that you can use any of the cert-manager's certificate backends, such as the in-cluster CA or HashiCorp Vault, and potentially reuse the same Issuer/ClusterIssuer with multiple instances.

Certificate rotation

Whether the certificates are managed by the operator or by cert-manager, they will be automatically renewed before expiration. Additionally, the operator will update the CA bundle whenever the CAs are rotated, temporarily retaining the old CA in the bundle to ensure a seamless update process.

In both scenarios, the standard update strategies apply, allowing you to control how the Pods are restarted during certificate rotation.

TLS requirements for `Users`

We have extended our User SQL resource to include TLS-specific requirements for user connections over TLS. For example, if you want to enforce the use of a valid x509 certificate for a user to connect:

apiVersion: k8s.mariadb.com/v1alpha1
kind: User
metadata:
  name: user
spec:
  ...
  require:
    x509: true

To restrict the subject of the user's certificate and/or require a specific issuer, you may set:

apiVersion: k8s.mariadb.com/v1alpha1
kind: User
metadata:
  name: user
spec:
  ...
  require:
    issuer: "/CN=mariadb-galera-ca"
    subject: "/CN=mariadb-galera-client"

If any of these TLS requirements are not satisfied, the user will be unable to connect to the instance.

Automatic updates when Galera options are changed

Whenever Galera options are changed, for example, adding providerOptions:

apiVersion: k8s.mariadb.com/v1alpha1
kind: MariaDB
metadata:
  name: mariadb-galera
spec:
  ...
  galera:
    enabled: true
+   providerOptions:
+     gcs.fc_limit: '64'

An update is now automatically triggered, and the Pods are restarted according to the configured update strategy.

Community contributions

Huge thanks to our awesome contributors! 🙇

We value your feedback! If you encounter any issues or have suggestions, please open an issue on GitHub. Your input is crucial to improve mariadb-operator🦭.

Join us on Slack: MariaDB Community Slack.

What's Changed

Fix TLS defaults in embedded MaxScale by @mmontes11 in https://github.com/mariadb-operator/mariadb-operator/pull/1143

Full Changelog: mariadb-operator/mariadb-operator@0.37.0...0.37.1

`v0.37.0`

Compare Source

[!WARNING]
A patch version 0.37.1 to fix a regression has been released. It is recommended to skip this version and upgrade to 0.37.1 instead

mariadb-operator 0.37.0 is here! 🦭

We're excited to introduce TLS 🔐 support in this release, one of the major features of mariadb-operator so far! ✨ Check out the TLS docs, our example catalog and the release notes below to start using it.

[!WARNING]
Be sure to follow the UPGRADE GUIDE to ensure a seamless transition from previous versions.

Issue certificates for `MariaDB` and `MaxScale`

Issuing and configuring TLS certificates for your instances has never been easier, you just need to set tls.enabled=true:

apiVersion: k8s.mariadb.com/v1alpha1
kind: MariaDB
metadata:
  name: mariadb-galera
spec:
  ...
  tls:
    enabled: true

apiVersion: k8s.mariadb.com/v1alpha1
kind: MaxScale
metadata:
  name: maxscale
spec:
  ...
  mariaDbRef:
    name: mariadb-galera
  tls:
    enabled: true

A self-signed Certificate Authority (CA) will be automatically generated to issue leaf certificates for your instances. The operator will also manage a CA bundle that your applications can use in order to establish trust.

TLS will be enabled by default in MariaDB, but it will not enforced. You can enforce TLS connections by setting tls.required=true to ensure that all connections are encrypted. In the case of MaxScale, TLS will only be enabled if you explicitly set tls.enabled=true or the referred MariaDB (via mariaDbRef) instance enforces TLS.

Native integration with cert-manager

cert-manager is the de facto standard for managing certificates in Kubernetes. This certificate controller simplifies the automatic provisioning, management, and renewal of certificates. It supports a variety of certificate backends (e.g. in-cluster, Hashicorp Vault), which are configured using Issuer or ClusterIssuer resources.

In your MariaDB and MaxScale resources, you can directly reference ClusterIssuer or Issuer objects to seamlessly issue certificates:

apiVersion: k8s.mariadb.com/v1alpha1
kind: MariaDB
metadata:
  name: mariadb-galera
spec:
  ...
  tls:
    enabled: true
    serverCertIssuerRef:
      name: root-ca
      kind: ClusterIssuer
    clientCertIssuerRef:
      name: root-ca
      kind: ClusterIssuer

apiVersion: k8s.mariadb.com/v1alpha1
kind: MaxScale
metadata:
  name: maxscale-galera
spec:
  ...
  tls:
    enabled: true
    adminCertIssuerRef:
      name: root-ca
      kind: ClusterIssuer
    listenerCertIssuerRef:
      name: root-ca
      kind: ClusterIssuer

Under the scenes, the operator will create cert-manager's Certificate resources with all the required Subject Alternative Names (SANs) required by your instances. These certificates will be automatically managed by cert-manager and the CA bundle will be updated by the operator so you can establish trust with your instances.

The advantage of this approach is that you can use any of the cert-manager's certificate backends, such as the in-cluster CA or HashiCorp Vault, and potentially reuse the same Issuer/ClusterIssuer with multiple instances.

Certificate rotation

Whether the certificates are managed by the operator or by cert-manager, they will be automatically renewed before expiration. Additionally, the operator will update the CA bundle whenever the CAs are rotated, temporarily retaining the old CA in the bundle to ensure a seamless update process.

In both scenarios, the standard update strategies apply, allowing you to control how the Pods are restarted during certificate rotation.

TLS requirements for `Users`

We have extended our User SQL resource to include TLS-specific requirements for user connections over TLS. For example, if you want to enforce the use of a valid x509 certificate for a user to connect:

apiVersion: k8s.mariadb.com/v1alpha1
kind: User
metadata:
  name: user
spec:
  ...
  require:
    x509: true

To restrict the subject of the user's certificate and/or require a specific issuer, you may set:

apiVersion: k8s.mariadb.com/v1alpha1
kind: User
metadata:
  name: user
spec:
  ...
  require:
    issuer: "/CN=mariadb-galera-ca"
    subject: "/CN=mariadb-galera-client"

If any of these TLS requirements are not satisfied, the user will be unable to connect to the instance.

Automatic updates when Galera options are changed

Whenever Galera options are changed, for example, adding providerOptions:

apiVersion: k8s.mariadb.com/v1alpha1
kind: MariaDB
metadata:
  name: mariadb-galera
spec:
  ...
  galera:
    enabled: true
+   providerOptions:
+     gcs.fc_limit: '64'

An update is now automatically triggered, and the Pods are restarted according to the configured update strategy.

Community contributions

Huge thanks to our awesome contributors! 🙇

We value your feedback! If you encounter any issues or have suggestions, please open an issue on GitHub. Your input is crucial to improve mariadb-operator🦭.

Join us on Slack: MariaDB Community Slack.

Run and operate MariaDB in a cloud native way

`v0.35.1`

Compare Source

Run and operate MariaDB in a cloud native way

`v0.35.0`

Compare Source

Run and operate MariaDB in a cloud native way

`v0.34.0`

Compare Source

Run and operate MariaDB in a cloud native way

`v0.33.0`

Compare Source

Run and operate MariaDB in a cloud native way

`v0.32.0`

Run and operate MariaDB in a cloud native way

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 becomes conflicted, 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 was generated by Mend Renovate. View the repository job log.

pmig · 2023-11-27T14:29:03Z

depends on #434

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

renovate bot added the dependencies label Oct 11, 2023

renovate bot changed the title ~~chore(deps): update helm release mariadb-operator to v0.21.0~~ chore(deps): update helm release mariadb-operator to v0.22.0 Oct 13, 2023

renovate bot force-pushed the renovate/mariadb-operator-0.x branch from e5fc648 to 1f9e3d6 Compare October 13, 2023 22:55

renovate bot force-pushed the renovate/mariadb-operator-0.x branch 3 times, most recently from 905adfe to 735d68b Compare October 31, 2023 17:14

renovate bot force-pushed the renovate/mariadb-operator-0.x branch from 735d68b to 3c301e2 Compare November 9, 2023 07:58

renovate bot changed the title ~~chore(deps): update helm release mariadb-operator to v0.22.0~~ chore(deps): update helm release mariadb-operator to v0.23.0 Dec 4, 2023

renovate bot force-pushed the renovate/mariadb-operator-0.x branch from 3c301e2 to ba7774e Compare December 4, 2023 20:22

renovate bot changed the title ~~chore(deps): update helm release mariadb-operator to v0.23.0~~ chore(deps): update helm release mariadb-operator to v0.23.1 Dec 4, 2023

renovate bot force-pushed the renovate/mariadb-operator-0.x branch 2 times, most recently from d2e430f to 23b9cd7 Compare December 11, 2023 08:17

renovate bot force-pushed the renovate/mariadb-operator-0.x branch 4 times, most recently from 129217d to d0cfce6 Compare December 18, 2023 17:03

renovate bot force-pushed the renovate/mariadb-operator-0.x branch from d0cfce6 to 59f60cd Compare December 28, 2023 18:21

renovate bot changed the title ~~chore(deps): update helm release mariadb-operator to v0.23.1~~ chore(deps): update helm release mariadb-operator to v0.24.0 Dec 28, 2023

renovate bot force-pushed the renovate/mariadb-operator-0.x branch 2 times, most recently from 7f4f6f4 to 28002e4 Compare January 8, 2024 14:04

renovate bot force-pushed the renovate/mariadb-operator-0.x branch 2 times, most recently from 6f391e5 to 51c715a Compare January 25, 2024 12:45

renovate bot force-pushed the renovate/mariadb-operator-0.x branch 4 times, most recently from 4dab2b2 to e2957c3 Compare February 10, 2024 12:59

renovate bot changed the title ~~chore(deps): update helm release mariadb-operator to v0.24.0~~ chore(deps): update helm release mariadb-operator to v0.25.0 Feb 10, 2024

renovate bot force-pushed the renovate/mariadb-operator-0.x branch from e2957c3 to dcccf40 Compare February 27, 2024 10:33

renovate bot changed the title ~~chore(deps): update helm release mariadb-operator to v0.25.0~~ chore(deps): update helm release mariadb-operator to v0.26.0 Mar 4, 2024

renovate bot force-pushed the renovate/mariadb-operator-0.x branch from 143f0f6 to 7fe72ba Compare September 13, 2024 16:14

renovate bot changed the title ~~chore(deps): update helm release mariadb-operator to v0.30.0~~ chore(deps): update helm release mariadb-operator to v0.31.0 Sep 13, 2024

renovate bot force-pushed the renovate/mariadb-operator-0.x branch from 7fe72ba to 46d244d Compare September 27, 2024 13:57

renovate bot changed the title ~~chore(deps): update helm release mariadb-operator to v0.31.0~~ chore(deps): update helm release mariadb-operator to v0.32.0 Sep 27, 2024

renovate bot force-pushed the renovate/mariadb-operator-0.x branch from 46d244d to 2899ff4 Compare September 27, 2024 17:05

renovate bot changed the title ~~chore(deps): update helm release mariadb-operator to v0.32.0~~ chore(deps): update helm release mariadb-operator to v0.33.0 Sep 27, 2024

renovate bot changed the title ~~chore(deps): update helm release mariadb-operator to v0.33.0~~ chore(deps): update helm release mariadb-operator to v0.34.0 Oct 7, 2024

renovate bot force-pushed the renovate/mariadb-operator-0.x branch 3 times, most recently from 0ba1b09 to 7d7d642 Compare October 8, 2024 09:00

renovate bot force-pushed the renovate/mariadb-operator-0.x branch 2 times, most recently from c77a3c2 to 85f8b0b Compare October 15, 2024 15:32

renovate bot changed the title ~~chore(deps): update helm release mariadb-operator to v0.34.0~~ chore(deps): update helm release mariadb-operator to v0.35.0 Oct 24, 2024

renovate bot force-pushed the renovate/mariadb-operator-0.x branch from 85f8b0b to 3cd46fb Compare October 24, 2024 14:04

renovate bot changed the title ~~chore(deps): update helm release mariadb-operator to v0.35.0~~ chore(deps): update helm release mariadb-operator to v0.35.1 Oct 25, 2024

renovate bot force-pushed the renovate/mariadb-operator-0.x branch from 3cd46fb to b4bae65 Compare October 25, 2024 16:58

renovate bot changed the title ~~chore(deps): update helm release mariadb-operator to v0.35.1~~ chore(deps): update helm release mariadb-operator to v0.36.0 Nov 8, 2024

renovate bot force-pushed the renovate/mariadb-operator-0.x branch from b4bae65 to b1af94f Compare November 8, 2024 12:22

renovate bot force-pushed the renovate/mariadb-operator-0.x branch from b1af94f to c5539f8 Compare January 28, 2025 13:35

renovate bot changed the title ~~chore(deps): update helm release mariadb-operator to v0.36.0~~ chore(deps): update helm release mariadb-operator to v0.37.0 Jan 28, 2025

renovate bot changed the title ~~chore(deps): update helm release mariadb-operator to v0.37.0~~ chore(deps): update helm release mariadb-operator to v0.37.1 Jan 29, 2025

renovate bot force-pushed the renovate/mariadb-operator-0.x branch from c5539f8 to eb471e1 Compare January 29, 2025 01:05

renovate bot force-pushed the renovate/mariadb-operator-0.x branch 3 times, most recently from 2efba98 to 57f7632 Compare March 6, 2025 11:04

renovate bot force-pushed the renovate/mariadb-operator-0.x branch from 57f7632 to 6890270 Compare March 26, 2025 21:51

renovate bot changed the title ~~chore(deps): update helm release mariadb-operator to v0.37.1~~ chore(deps): update helm release mariadb-operator to v0.38.0 Mar 26, 2025

chore(deps): update helm release mariadb-operator to v0.38.1

5c126f8

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

renovate bot force-pushed the renovate/mariadb-operator-0.x branch from 6890270 to 5c126f8 Compare April 15, 2025 20:05

renovate bot changed the title ~~chore(deps): update helm release mariadb-operator to v0.38.0~~ chore(deps): update helm release mariadb-operator to v0.38.1 Apr 15, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): update helm release mariadb-operator to v0.38.1 #363

chore(deps): update helm release mariadb-operator to v0.38.1 #363

Uh oh!

renovate bot commented Oct 11, 2023 •

edited

Loading

Uh oh!

pmig commented Nov 27, 2023 •

edited

Loading

Uh oh!

Uh oh!

chore(deps): update helm release mariadb-operator to v0.38.1 #363

Are you sure you want to change the base?

chore(deps): update helm release mariadb-operator to v0.38.1 #363

Uh oh!

Conversation

renovate bot commented Oct 11, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Issue certificates for MariaDB and MaxScale

Native integration with cert-manager

Certificate rotation

TLS requirements for Users

Automatic updates when Galera options are changed

Community contributions

What's Changed

Issue certificates for MariaDB and MaxScale

Native integration with cert-manager

Certificate rotation

TLS requirements for Users

Automatic updates when Galera options are changed

Community contributions

What's Changed

New Contributors

Configuration

Uh oh!

pmig commented Nov 27, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

renovate bot commented Oct 11, 2023 •

edited

Loading

Issue certificates for `MariaDB` and `MaxScale`

TLS requirements for `Users`

Issue certificates for `MariaDB` and `MaxScale`

TLS requirements for `Users`

pmig commented Nov 27, 2023 •

edited

Loading