feat(mariadb): default-on reconnectOnAuthError for replica auth self-heal (0.1.28) - #70
Merged
Merged
Conversation
…heal Render spec.replication.replica.recovery when either recovery.enabled OR recovery.reconnectOnAuthError is set (previously enabled-only), emit the actual enabled value, and add reconnectOnAuthError (default true). Lets a replica stuck on repl auth error 1045 self-heal via the operator without enabling the heavy backup-rebuild recovery. Requires the operator's reconnectOnAuthError build. Bump 0.1.27 -> 0.1.28.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds opt-in replica auth self-heal support to the
mariadbchart, defaulted on, to pair with the operator's newreconnectOnAuthErrorfeature (ubc/mariadb-operator#4).When a replica's IO thread is stuck on repl auth error 1045 (
Access denied for user 'repl') pasterrorDurationThreshold, the operator re-issuesCHANGE MASTERwith the current secret — a lightweight re-sync (no backup rebuild) that only touches an already-broken replica.Changes (
mariadbchart,0.1.27→0.1.28)templates/mariadb.yaml: renderspec.replication.replica.recoverywhen eitherrecovery.enabledorrecovery.reconnectOnAuthErroris set (wasenabled-only), emit the realenabledvalue (was hardcodedtrue), and addreconnectOnAuthError.values.yaml: addsecondary.replica.recovery.reconnectOnAuthError: true(default-on).Behavior
recovery: { enabled: false, errorDurationThreshold: 5m, reconnectOnAuthError: true }—enabled: falsekeeps the heavy backup-rebuild recovery off; satisfies the CRD's requiredenabledfield.recoveryblock).reconnectOnAuthErrorbuild (feat(replication): self-heal replicas stuck on repl auth error 1045 (opt-in) mariadb-operator#4, already deployed to appcloud).Verified
helm template … --set architecture=replication→ correct recovery block.helm lintclean.Follow-up (sequential — after this merges & publishes)
The
hotcrpchart'sChart.lockpinsmariadbat0.1.27, so it can only re-resolve theversion: "*"db dependency to0.1.28after0.1.28is published. Once this merges:helm dependency update hotcrp(re-resolves lock →mariadb 0.1.28) + bumphotcrpchart version, publish.revisionindevops/configuration→ ArgoCD sync → hotcrp MariaDB CRs gain the flag.Every other replicated DB on this chart picks it up automatically on its next chart republish (default-on +
version: "*").https://claude.ai/code/session_01BCHp8v87idhtUwTJ5XJ5qu