oxidecomputer / oxidecomputer/omicron
DNS aliases
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
In the Dogfood deployment we've got a custom DNS name, not the rack-provided one. I suspect many customers will want to be able to do this. I'm figuring we could add a "dns_alias" property on the Silo that can be set to any DNS name you want.
We will also need to update the TLS SNI implementation in #3164 to choose the right TLS certificate for the DNS name we were given.
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 Silo model and the TLS SNI implementation referenced in #3164. Trace how a custom DNS name could be stored and how the matching certificate would be selected. Done means a Silo can accept a dns_alias and TLS SNI selects the corresponding certificate for that name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100