How To Expose the Linkerd2 Dashboard Securely
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 221
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 1
Description
### What is the purpose of the post?
A tutorial to explain how you can expose the Linkerd2 dashboard securely
### What should it talk about?
* What problem does exposing the dashboard solve?
* What use cases does it address?
* What are the various options for exposing the Linkerd2 dashboard?
**What are the positives and negatives of each option?
* How does an end user expose the Linkerd2 dashboard in their own project?
### Who is the target audience?
* [ ] Architect
* [x] SRE
* [x] Developers
### Are there any assets?
This should take the form of a tutorial and include specific applicable CLI commands and sequences to expose the dashboard. Using GIFs or codescreens to display the requisite actions is recommended. .
### What are the dependencies?
TBD - depends on what the author thinks are appropriate here.
### Relevant Examples / References
https://stackoverflow.com/questions/39864385/how-to-access-expose-kubernetes-dashboard-service-outside-of-a-cluster
https://blog.heptio.com/on-securing-the-kubernetes-dashboard-16b09b1b7aca
https://www.thehumblelab.com/deploying-kubernetes-dashboard-in-the-lab/
Contributor guide
Research direction
Start by reviewing the issue’s requested tutorial topics and the three linked Kubernetes dashboard references. Determine the supported secure exposure options and their trade-offs, then document applicable CLI command sequences for SREs and developers. Done means the tutorial explains the problem, use cases, options, security considerations, and end-user steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100