Standalone overlord

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
kubernetes, rust
Domain
distributed-systems, infrastructure

Research direction

The issue names no files, tests, or entry points. Start by locating how the operator currently deploys the coordinator and overlord in separate processes or pods, then define the expected standalone deployment behavior and validation before making changes.

Written by the indexing model from the issue text.

Description

The coordinator supports running the overlord itself, which is how we do it at the moment.

It might be useful to some to have it run in a seperate process/pod.

supposedly seperating them makes Druid more resilient.

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.