Operator fails "silently" to update Druid Cluster's resource

Open
#438 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
kubernetes, rust

Research direction

Start at the custom resource reconciliation path for Druid cluster resource changes and trace how the StatefulSet handles data storage size updates. Reproduce a data-storage change and compare it with CPU or memory changes; done means the operator applies the storage change without silently leaving the StatefulSet unchanged, while preserving the PVCs.

Written by the indexing model from the issue text.

Description

customer-request type/bug
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

Dominant language
Rust
Stars
12
Forks
1
Avg merge
1d 17h
Merged PRs (30d)
10

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/druid-operator

All issues in stackabletech/druid-operator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.