stackabletech / stackabletech/druid-operator
Add correct probes to Druid containers
Open
Nobody has claimed this yet.
status/blocked
- Dominant language
- Rust
- Stars
- 12
- Forks
- 1
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 10
Description
We could use the /status/health endpoint or others (/druid/broker/v1/readiness for the broker and historical) to implement readiness probes.
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 tracing where the operator defines Druid containers and their Kubernetes probes. Compare the available /status/health endpoint with /druid/broker/v1/readiness for broker and historical components, then verify that the resulting readiness behavior is covered by the project's existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100