Issue on docs
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 11
- Forks
- 76
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 26
Description
Path: /omni/self-hosted/run-omni-on-prem
Would be useful to include steps to get Omni self-signed CA onto existing Talos nodes so that Siderolink can function and existing Talos nodes can be imported.
talosctl patch mc --patch @trusted-omni-ca.yaml -n <talos-node>
CA Cert used by Omni will not be trusted by Talos nodes - therefore will not be able to establish SideroLink
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
Open /omni/self-hosted/run-omni-on-prem and review the existing self-hosted setup steps. Add instructions for applying the Omni self-signed CA to existing Talos nodes, including the provided talosctl patch command, so readers understand how to enable SideroLink and import those nodes. Done when the page documents this prerequisite clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 85/100