Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feat(container): update image ghcr.io/mariadb-operator/mariadb-operator to v0.36.0 #1055

Merged
merged 1 commit into from
Nov 12, 2024
Merged

feat(container): update image ghcr.io/mariadb-operator/mariadb-operator to v0.36.0 #1055

merged 1 commit into from
Nov 12, 2024

Conversation

spicerabot[bot]
Copy link
Contributor

@spicerabot spicerabot bot commented Oct 24, 2024 •
edited
Loading

This PR contains the following updates:

Package Update Change
ghcr.io/mariadb-operator/mariadb-operator minor 0.34.0 -> 0.36.0

Warning

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

Release Notes

mariadb-operator/mariadb-operator (ghcr.io/mariadb-operator/mariadb-operator)

v0.36.0

Compare Source

mariadb-operator 0.36.0 is here! 🦭

We're thrilled to announce this new release packed with multiple enhancements contributed by our community members. A community-driven release like this one is the best way to celebrate that we are already more than 50 contributors 🎉:

If you're upgrading from previous versions, don't miss the UPGRADE GUIDE for a smooth transition.

Replication (alpha)

Backup

Services

SQL

Huge thanks to our awesome contributors @​hedgieinsocks, @​onesolpark, @​johanjk, and @​P4sca1 for making this release possible! 🙇

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

New Contributors

Full Changelog: mariadb-operator/mariadb-operator@0.35.1...0.36.0

v0.35.1

Compare Source

0.35.1 is a patch release with a focused scope, aimed at stabilizing Galera cluster recovery and enhancing our new Kubernetes custom types. For an overview of features introduced in this release series, see the 0.35.0 release notes.

To upgrade from older versions, be sure to follow the UPGRADE GUIDE.

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

Full Changelog: mariadb-operator/mariadb-operator@0.35.0...0.35.1

v0.35.0

Compare Source

mariadb-operator 0.35.0 is out! 🦭

To upgrade from older versions, be sure to follow the UPGRADE GUIDE.

Staging storage for S3 backups

When using S3 storage for backups, a staging area is used for keeping the external backups while they are being processed. By default, this staging area is an emptyDir volume, which means that the backups are temporarily stored in the node's local storage where the Backup/Restore Job is scheduled. In production environments, large backups may lead to issues if the node doesn't have sufficient space, potentially causing the backup/restore process to fail.

To overcome this limitation, you are now able to define your own staging area by setting the stagingStorage field to both the Backup and Restore CRs:

apiVersion: k8s.mariadb.com/v1alpha1
kind: Backup
metadata:
  name: backup
spec:
  storage:
    s3:
      ...
  stagingStorage:
    persistentVolumeClaim:
      resources:
        requests:
          storage: 10Gi
      accessModes:
        - ReadWriteOnce
apiVersion: k8s.mariadb.com/v1alpha1
kind: Restore
metadata:
  name: restore
spec:
  s3:
    ...
  stagingStorage:
    persistentVolumeClaim:
      resources:
        requests:
          storage: 10Gi
      accessModes:
        - ReadWriteOnce

In the examples above, a PVC with the default StorageClass will be used as staging area. Refer to the API reference for more configuration options.

More flexibility configuring Kubernetes types

We have recently slimmed down our CRDs, resulting in a ~81% size decrease. As part of this massive refactor, we have replaced the upstream Kubernetes types and introduce our custom types. In this release, we keep committed to this matter, and we have extended our Kubernetes types to ensure flexibility, including:

  • nodeAffinity as expression-driven alternative to nodeSelector
  • configMap and secret volume sources support
  • env support for both initContainers and sidecarContainers
  • resources support in metrics exporter Deployment

Refer to the API reference for more details about this fields.

Kudos to @​am6737 for helping with this! 🙏🏻

Enhanced session affinity for MaxScale GUI

In previous releases, the MaxScale GUI Service used sessionAffinity to avoid load balancing, ensuring that GUI requests stayed with the same Pod. This was important because each MaxScale Pod operates as an independent server, maintaining its own user sessions for the GUI.

When using an API gateway in front of the MaxScale GUI Service without sessionAffinity configured, users may experience unexpected logouts, as sessions from one server are invalid on another. To address this, we now point the MaxScale GUI Service to a specific Pod, dynamically updating the target if the selected Pod goes down. This approach ensures consistency and predictability, minimizing the chances of sending GUI requests to new MaxScale Pods whenever possible. See https://github.com/mariadb-operator/mariadb-operator/pull/956.

Refer to the MaxScale docs for further detail.

Support for image digests in Helm chart

You can now specify image digests when installing the operator Helm chart. Instead of providing a tag, you will need to specify a digest under the image values:

image:
  repository: docker-registry3.mariadb.com/mariadb-operator/mariadb-operator
  pullPolicy: IfNotPresent
  digest: sha256:084a927ee9f3918a5c85d283f73822ae205757df352218de0b935853a0765060

webhook:
  enabled: true
  image:
    repository: docker-registry3.mariadb.com/mariadb-operator/mariadb-operator
    pullPolicy: IfNotPresent
    digest: sha256:084a927ee9f3918a5c85d283f73822ae205757df352218de0b935853a0765060

certController:
  enabled: true
  image:
    repository: docker-registry3.mariadb.com/mariadb-operator/mariadb-operator
    pullPolicy: IfNotPresent
    digest: sha256:084a927ee9f3918a5c85d283f73822ae205757df352218de0b935853a0765060

Kudos to @​am6737 for this contribution! 🙏🏻

Replication improvements

During an update, make sure that at least one Pod has replication configured before proceeding with the update of the primary. See https://github.com/mariadb-operator/mariadb-operator/pull/947.

Kudos to @​BonySmoke for this contribution! 🙏🏻

Various fixes

See https://github.com/mariadb-operator/mariadb-operator/pull/932 https://github.com/mariadb-operator/mariadb-operator/pull/924.

Kudos to @​am6737 for these contributions! 🙏🏻

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

New Contributors

Full Changelog: mariadb-operator/mariadb-operator@v0.0.32...0.35.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 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 has been generated by Renovate Bot.

@spicerabot spicerabot bot requested a review from spiceratops as a code owner October 24, 2024 13:11
@spicerabot
Copy link
Contributor Author

spicerabot bot commented Oct 24, 2024 •
edited
Loading 

--- kubernetes/apps/databases/mariadb-operator/operator Kustomization: flux-system/mariadb-operator HelmRelease: databases/mariadb-operator

+++ kubernetes/apps/databases/mariadb-operator/operator Kustomization: flux-system/mariadb-operator HelmRelease: databases/mariadb-operator

@@ -25,13 +25,13 @@

     ha:
       enabled: true
       replicas: 3
     image:
       pullPolicy: IfNotPresent
       repository: ghcr.io/mariadb-operator/mariadb-operator
-      tag: 0.34.0
+      tag: 0.36.0
     resources:
       limits:
         memory: 1024M
       requests:
         cpu: 50m
         memory: 128M

@spicerabot
Copy link
Contributor Author

spicerabot bot commented Oct 24, 2024 •
edited
Loading 

--- HelmRelease: databases/mariadb-operator Deployment: databases/mariadb-operator

+++ HelmRelease: databases/mariadb-operator Deployment: databases/mariadb-operator

@@ -20,13 +20,13 @@

         app.kubernetes.io/instance: mariadb-operator
     spec:
       serviceAccountName: mariadb-operator
       automountServiceAccountToken: true
       terminationGracePeriodSeconds: 10
       containers:
-      - image: ghcr.io/mariadb-operator/mariadb-operator:0.34.0
+      - image: ghcr.io/mariadb-operator/mariadb-operator:0.36.0
         imagePullPolicy: IfNotPresent
         name: controller
         args:
         - --metrics-addr=:8080
         - --log-level=INFO
         - --leader-elect

@spicerabot spicerabot bot force-pushed the renovate/ghcr.io-mariadb-operator-mariadb-operator-0.x branch from 7164f3e to c129024 Compare October 25, 2024 16:08
@spicerabot spicerabot bot changed the title feat(container): update image ghcr.io/mariadb-operator/mariadb-operator to v0.35.0 feat(container): update image ghcr.io/mariadb-operator/mariadb-operator to v0.35.1 Oct 25, 2024
@spicerabot spicerabot bot force-pushed the renovate/ghcr.io-mariadb-operator-mariadb-operator-0.x branch from c129024 to 84c4250 Compare November 8, 2024 12:12
@spicerabot spicerabot bot changed the title feat(container): update image ghcr.io/mariadb-operator/mariadb-operator to v0.35.1 feat(container): update image ghcr.io/mariadb-operator/mariadb-operator to v0.36.0 Nov 8, 2024
@spicerabot spicerabot bot force-pushed the renovate/ghcr.io-mariadb-operator-mariadb-operator-0.x branch from 84c4250 to 1403a58 Compare November 12, 2024 06:09
@spiceratops spiceratops merged commit 5938172 into main Nov 12, 2024
6 of 8 checks passed
@spiceratops spiceratops deleted the renovate/ghcr.io-mariadb-operator-mariadb-operator-0.x branch November 12, 2024 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@spiceratops spiceratops Awaiting requested review from spiceratops spiceratops is a code owner

Assignees

@spiceratops spiceratops

Labels
area/kubernetes renovate/container type/minor
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@spiceratops