Skip to content

Commit

Permalink
Add TLS section to prerequisites (#113)
Browse files Browse the repository at this point in the history
  • Loading branch information
mkjpryor authored Mar 1, 2024
1 parent fa3faaf commit 19053f1
Showing 1 changed file with 12 additions and 0 deletions.
12 changes: 12 additions & 0 deletions docs/configuration/01-prerequisites.md
Original file line number Diff line number Diff line change
Expand Up @@ -116,3 +116,15 @@ being deployed with a floating IP attached that routes traffic to the ingress co
In order for traffic to be routed correctly for these domains, a **wildcard** DNS record must exist
for `*.azimuth.example.org` that points at the floating IP of the load-balancer for the ingress
controller. **Azimuth does not manage this DNS record.**

## Transport Layer Security (TLS)

In order to provide secure connections to users, Azimuth needs to be able to obtain a TLS
certificate and private key for any of the subdomains under its wildcard domain.

This can be achieved in two ways:

1. Using a pre-existing wildcard TLS certificate for all subdomains
2. Using an ACME server (e.g. Let's Encrypt) to issue certificates dynamically

These approaches are discussed in more detail in the [Ingress section](../configuration/06-ingress.md).

0 comments on commit 19053f1

Please sign in to comment.