Repository navigation
Conversation
Their only caller, the ConfigMap resume handler, was removed in 0c7478e. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
The exporter image and configuration were only written when a cluster was created, so sql_exporter bumps never reached existing clusters without manual kubectl work. With SQL_EXPORTER_AUTO_UPDATE enabled, a resume handler updates the ConfigMap, restarts only the sql-exporter container one pod at a time, and then patches the StatefulSets. An image that does not start is reverted on the first pod and not retried until the operator restarts. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
goat-ssh
marked this pull request as draft
November 13, 2026 11:28
This branch has not been deployed
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
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 of changes
On top of #931
SQL exporter image and configuration were only written when a cluster was created, so version upgrades were manual action.
With new env var
SQL_EXPORTER_AUTO_UPDATEenabled, a resume handler updates theConfigMap, restarts only the sql-exporter container one pod at a time, and then patches the StatefulSets.
An image that does not start is reverted on the first pod and not retried until the operator restarts.
🤖
Checklist
CHANGES.rst