OpenUnison / OpenUnison/openunison.github.io
Manual deployment method fails to explain how to create the ou-tls-certificate and unison-tls secrets
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 6
- Avg merge
- 5h 10m
- Merged PRs (30d)
- 1
Description
I tried to follow the manual deployment steps, but the kube-oidc-proxy-orchestra pod cannot be created, as the secrets ou-tls-certificate and unison-tls are missing.
The docs mention that one can get something out of the ou-tls-certificate, but not how to create them.
Or, when they will be required, aka which options in the values.yaml require those secrets.
Could this be added?
Contributor guide
No contributing guide indexed for this repository
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 manual deployment instructions and values.yaml, then trace where the kube-oidc-proxy-orchestra pod expects the ou-tls-certificate and unison-tls secrets. Document how to create both secrets and identify which values.yaml options require them; done means a manual deployment can follow the updated instructions without missing these secrets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100