How to enable TLS for each product?
Open
Nobody has claimed this yet.
security
tls
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
Right now we presume that most users will terminate TLS at an ingress and then run the products in HTTP.
We should start getting a roadmap for what it would take to make TLS support "first class" in Kubernetes.
- Proposed paradigm / configuration
- Consistency at some level across the charts
- Ability to use
Certificateresources / etc. on the cluster? - Product features necessary to enable this workflow?
- Changed values / defaults to make the helm chart configuration experience reasonable
- Examples and documentation
- need to include
launcher(#226) - Need to include sessions
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 repository's Helm charts and the Kubernetes TLS and Certificate resource patterns referenced in the issue. Done requires an agreed configuration paradigm, consistent chart behavior across products including launcher and sessions, product support, sensible values and defaults, and examples and documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100