DNS module
Layer 10. Edge. Edge Records publish a deployment outside the cluster.
Source: modules/dns/.
At a glance
Section titled “At a glance”| CLI | None |
| Subcommands | 0 |
| HTTP endpoints | see the route reference |
| Events emitted | None |
| Error codes | see the error code reference |
| Service classes | DNSService |
| Cross-module deps | None |
Source layout
Section titled “Source layout”modules/dns/├── service.go└── providers/Errors
Section titled “Errors”Typed errors are catalogued in the error code reference with HTTP statuses and message templates.
Responsibilities
Section titled “Responsibilities”The dns module owns per-deployment DNS records: creating,
updating, and tearing down the entries that expose a running deployment.
Providers are pluggable (see dns/providers/).
DNSService is called by the app lifecycle (install /
uninstall / ingress changes) and by cluster-level DNS sync (see
cluster/dns-provider-sync). It does
not own ingress rules (those live in modules/app/ingress_materialize.go).
shc@docs:~$