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

redpanda: don't set cluster config values in redpanda.yaml #1524

Open
wants to merge 1 commit into
base: chris/p/gotohelm-stringish-keys
Choose a base branch
from

Conversation

chrisseto
Copy link
Contributor

Prior to this commit, cluster config values were being set in redpanda.yaml. This was being done as a historical artifact of redpanda <= 22.1 1.

While doing so is largely benign it clutters the, already quite busy, redpanda.yaml and can result in unnecessary restarts when only changing cluster configurations.

This commit:

  • Removes cluster configurations from redpanda.yaml
  • Updates the config hash on the StatefulSet to only be computed from redpanda.yaml. This allows users to update cluster configurations from the chart without initiating a rolling restart.

Fixes #1345

Prior to this commit, cluster config values were being set in redpanda.yaml.
This was being done as a historical artifact of redpanda <= 22.1 [1].

While doing so is largely benign it clutters the, already quite busy,
redpanda.yaml and can result in unnecessary restarts when only changing cluster
configurations.

This commit:
- Removes cluster configurations from redpanda.yaml
- Updates the config hash on the StatefulSet to only be computed from
  `redpanda.yaml`. This allows users to update cluster configurations from the
  chart without initiating a rolling restart.

Fixes #1345

[1]: https://www.redpanda.com/blog/raft-centralized-cluster-configuration-improvements
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.

1 participant