Which Services/roles need to be exposed?

Open
#465 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
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
kubernetes, rust
Domain
infrastructure

Research direction

No source files or tests are identified. First review how the five role-level Services are currently exposed, then use the linked Druid mailing-list discussion to determine which roles clients need. Done means the intended exposure and access structure are agreed and documented for implementation.

Written by the indexing model from the issue text.

Description

Currently, we deploy a role level Service for each of the 5 roles we have. But most commonly only the router needs to be accessed by clients. In some cases, clients might want to access the Broker and Coordinator.

We should find out which roles need to be exposed, and restructure access accordingly.

I have sent an email to the druid mailinglist: https://groups.google.com/g/druid-user/c/el4BFpJfcWA

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.