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.

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

MariaDB-Operator updates #114

Merged
merged 3 commits into from
Mar 8, 2024
Merged

Conversation

cloudnull
Copy link
Contributor

@cloudnull cloudnull commented Mar 6, 2024

This change is updating the mariadb-galera manifest to use the latest images
and system config. This is being done to help resolve some of the deadlock
issues being experienced when the cluster is under load.

This change also brings in a LOT of fixes into the operator, which should
help make our platform run better, generally.

All of the CRD references have been updated to use the stable release of the
operator, version 0.26.0.

@BjoernT
Copy link
Collaborator

BjoernT commented Mar 6, 2024

The rook submodule changed, was that an accident, ie not rebasing?

Copy link
Collaborator

@BjoernT BjoernT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The rook submodule changed, was that an accident, ie not rebasing?

BjoernT
BjoernT previously requested changes Mar 6, 2024
kustomize/mariadb-cluster/base/mariadb-galera.yaml Outdated Show resolved Hide resolved
kustomize/mariadb-cluster/base/mariadb-galera.yaml Outdated Show resolved Hide resolved
@cloudnull
Copy link
Contributor Author

The rook submodule changed, was that an accident, ie not rebasing?

good catch, rebased and fixed.

Nothing in our stack uses the mariadb-operator submodule from our local path.
This change eliminates the submodule because we've no reason to keep it.

Signed-off-by: Kevin Carter <[email protected]>
@cloudnull cloudnull force-pushed the operator-update branch 2 times, most recently from e8197b1 to 94db186 Compare March 7, 2024 06:12
This change is updating the mariadb-galera manifest to use the latest images
and system config. This is being done to help resolve some of the deadlock
issues being experienced when the cluster is under load.

This change also brings in a LOT of fixes into the operator, which should
help make our platform run better, generally.

All of the CRD references have been updated to use the stable release of the
operator, version 0.26.0.

> Metrics were enabled by default now that we're metric collection is on deployed.

Signed-off-by: Kevin Carter <[email protected]>
@cloudnull cloudnull dismissed BjoernT’s stale review March 8, 2024 15:56

pushed new updates.

@sulochan
Copy link
Collaborator

sulochan commented Mar 8, 2024

LGTM

Install works. I did not try to upgrade. v0.0.26 upgrade has breaking changes, so if we are planning to upgrade, we need docs on that.

Reference:

https://github.com/mariadb-operator/mariadb-operator/blob/28bfbe15e1364764c427660bf365dc802fa0f00e/docs/UPGRADE_v0.0.26.md

@cloudnull cloudnull merged commit 4955a97 into rackerlabs:main Mar 8, 2024
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants