Launcher SSL
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
We are working on a deployment where all three products will be running on one single Kubernetes Cluster, I am having a bit of a hard time getting launcher to work with SSL. In our launcher.conf file and rserver.conf files, should we be specifying localhost as the Launcher address?
address=localhost
port=5559
or should it be our workbench url
address=workbench.domain.com
port=5559
and for the SSL Cert, does it need to be issued to localhost?
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 with the launcher.conf and rserver.conf examples in the issue, then trace how the Launcher address, port 5559, and SSL certificate are used in the Kubernetes deployment. Confirm the expected configuration for a single cluster and document what a working SSL connection should use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100