StackGuardian / StackGuardian/tirith
research(positioning): Kubernetes admission-policy comparison
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 165
- Forks
- 42
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 11
Description
A document, not code: map Tirith against the in-cluster Kubernetes admission-policy engines and
their policy kinds (validate, mutate, generate, cleanup, image verification). Expected shape:
admission engines own the in-cluster moment; Tirith's axis is the change (plan, before/after,
blast radius) and multi-document correlation; mutation/generation are explicitly out of scope.
Contributor guide
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
Use the issue's requested comparison as the outline; begin by researching in-cluster Kubernetes admission-policy engines and their policy kinds. Keep the document centered on admission-time ownership versus Tirith's change-oriented axis and multi-document correlation, with mutation and generation explicitly out of scope. Done when each requested policy kind is mapped clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100