Skip to content

Fix secret-backed env upgrade rollout - #1966

Merged
sunsingerus merged 1 commit into
0.27.0from
fix/secret-backed-upgrade-rollout
Apr 24, 2026
Merged

sunsingerus merged 1 commit into
0.27.0from
fix/secret-backed-upgrade-rollout

Conversation

@alex-zaitsev

@alex-zaitsev alex-zaitsev commented Apr 24, 2026 •

Copy link
Copy Markdown
Member

What changed

  • avoid forcing a software restart before StatefulSet reconciliation when the desired pod template has changed
  • fall back to a StatefulSet rollout for secret-backed environment updates that require a pod template refresh

Why

When a CHI update adds a secret-backed environment variable and also starts using that variable from ClickHouse config, forcing a software restart first can restart the existing pod before the StatefulSet rollout has injected the new env var. That can leave the pod failing during reconciliation instead of letting the template change roll out cleanly.

Closes #1963

@alex-zaitsev
alex-zaitsev marked this pull request as ready for review April 24, 2026 08:11

@sunsingerus sunsingerus left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Approving. Review comments (doc comment, unit test for hostRequiresStatefulSetRollout, log message clarity, CHK parity) to be addressed in follow-ups after merge.

@sunsingerus
sunsingerus merged commit 1f4115b into 0.27.0 Apr 24, 2026
1 of 2 checks passed
@sunsingerus
sunsingerus deleted the fix/secret-backed-upgrade-rollout branch June 4, 2026 16:43
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.

2 participants