Threat Model for linkerd single/multi cluster
Open
Nobody has claimed this yet.
pinned
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
## Feature Request
Provide threat model for linkerd single/multi cluster similar to [k8s-threat-model](https://github.com/cncf/financial-user-group/tree/master/projects/k8s-threat-model)
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
Start by reviewing the referenced k8s-threat-model and Linkerd's single- and multi-cluster scope. Define the threats and trust boundaries for both deployment modes, then document the resulting threat model in the repository; done means both modes are covered in a published, reviewable document.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100