redpanda-data / redpanda-data/redpanda-operator
re-visit the need to restart the schema registry service after performing updates
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 84
- Forks
- 32
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 104
Description
The helm chart's post upgrade hook performs a restart of the schema registry service utilizing the admin api's debug endpoints. It's suspected that this is being performed to handle transitions to and from SASL being enabled on the cluster but we're not 100% certain about this.
We need to add some tests that enable and then disable SASL so we can assert whether or not such a hook is required for stable operations.
See Also:
- https://github.com/redpanda-data/redpanda-operator/pull/231
- https://github.com/redpanda-data/helm-charts/pull/846
JIRA Link: K8S-361
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Helm chart's post-upgrade hook and the admin API debug endpoints it uses. Add tests that enable and disable SASL, then verify whether stable operations require the restart hook and use those results to determine the expected hook behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- devops, security, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100