Add correct probes to Druid containers

Open
#142 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #273 by @sbernauer — closed without merging
  • #276 by @sbernauer — closed without merging

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
kubernetes, rust
Domain
devops, infrastructure

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.

Description

status/blocked

We could use the /status/health endpoint or others (/druid/broker/v1/readiness for the broker and historical) to implement readiness probes.

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.