stackabletech / stackabletech/kafka-operator
Operator fails "silently" to update Kafka Cluster's resource
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 28
- Forks
- 8
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 9
Description
Affected version
No response
Current and expected behavior
I could recreate the problem when changing the "data" storage size.Changing CPU or Memory resources seems to work (results in a Pod restart).
Possible solution
In order to capture this we either need webhooks or track the resources in the status of the custom resource and delete and recreate the statefulset (PVCs should be resized automatically?).
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
None
Contributor guide
No contributing guide indexed for this repository
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 by reproducing the reported failure when changing a Kafka Cluster's data storage size, then trace how the operator handles resource changes compared with CPU or memory changes. Done means the data storage update is no longer silently ignored and the resulting Kafka resources behave as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kafka, kubernetes, rust
- Domain
- distributed-systems, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100