Operator overview pages for internal operators (commons, secret, listener)

Open
#408 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
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Start by reading follow-up issue #282 and inspect the existing documentation for the commons, secret, and listener operators. For each operator, document its roles, created and retained or removed resources, dependencies, diagrams, and demo links. The work is done when all three operator checkboxes are covered.

Written by the indexing model from the issue text.

Description

area/documentation size/M

Follow up to https://github.com/stackabletech/documentation/issues/282

Explain for every operator:

  • which roles does it have and what do they mean?
  • Which resources does it create:
    • i.e. statefulsets per role
    • configmap for discovery
  • also a diagram
  • which resources does it tear down again?
    • for example, ConfigMaps and PVCs are staying
  • what are the dependencies, what other operators does it connect to?
  • link to demos

Operators:

  • commons
  • secret
  • listener
Dominant language
CSS
Stars
13
Forks
14
Avg merge
4d 8h
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/documentation

All issues in stackabletech/documentation

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.