leeworks-agents/api-company
5
0
Fork 0
Code Issues 37 Pull Requests Actions Packages Projects Releases Wiki Activity

docs: add grafana.leeworks.dev as 7th DNS record in dns.md and operator-runbook

Browse Source 
- dns.md: fix '6 A records' wording to '7 A records'
- dns.md: add grafana.leeworks.dev to status checklist and dig verification block
- operator-runbook.md: fix 'all six' to 'all seven', add registry.leeworks.dev
  row to Phase 4 DNS table, add dig verification loop

Closes leeworks-agents/api-company#62
This commit is contained in:
agent-company
2026-05-27 15:04:13 +00:00
parent 13ce96e07e
commit 8902feada7
2 changed files with 15 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/dns.md
+4 -2
View File
@@ -102,6 +102,7 @@ dig aqi.leeworks.dev +short
dig docs.leeworks.dev +short dig docs.leeworks.dev +short
dig status.leeworks.dev +short dig status.leeworks.dev +short
dig registry.leeworks.dev +short dig registry.leeworks.dev +short
dig grafana.leeworks.dev +short
# Check TLS certificates (once services are deployed) # Check TLS certificates (once services are deployed)
curl -v https://zip.leeworks.dev/health 2>&1 | grep -E "SSL|certificate|issuer" curl -v https://zip.leeworks.dev/health 2>&1 | grep -E "SSL|certificate|issuer"
@@ -125,7 +126,7 @@ The following actions require human operator access to the DNS provider:
1. Log into the DNS provider managing `leeworks.dev` 1. Log into the DNS provider managing `leeworks.dev`
2. Find the cluster ingress IP: `kubectl get svc -n ingress-nginx ingress-nginx-controller` 2. Find the cluster ingress IP: `kubectl get svc -n ingress-nginx ingress-nginx-controller`
3. Create/update the 6 A records listed in the table above 3. Create/update the 7 A records listed in the table above
4. Verify propagation: `dig +trace zip.leeworks.dev` 4. Verify propagation: `dig +trace zip.leeworks.dev`
DNS propagation typically takes 5–60 minutes. DNS propagation typically takes 5–60 minutes.
@@ -141,4 +142,5 @@ DNS propagation typically takes 5–60 minutes.
- [ ] `docs.leeworks.dev` → DNS record created - [ ] `docs.leeworks.dev` → DNS record created
- [ ] `status.leeworks.dev` → DNS record created - [ ] `status.leeworks.dev` → DNS record created
- [ ] `registry.leeworks.dev` → DNS record created - [ ] `registry.leeworks.dev` → DNS record created
- [ ] TLS certificates issued and valid for all 6 subdomains - [ ] `grafana.leeworks.dev` → DNS record created
- [ ] TLS certificates issued and valid for all 7 subdomains
docs/operator-runbook.md
+11 -1
View File
@@ -188,7 +188,7 @@ kubectl create secret generic gitea-image-automation-token \
## Phase 4 — DNS for API services (issue #33) ## Phase 4 — DNS for API services (issue #33)
Add DNS A records for all six leeworks.dev subdomains (all point to the same Add DNS A records for all seven leeworks.dev subdomains (all point to the same
cluster ingress IP): cluster ingress IP):
| Hostname | Target | | Hostname | Target |
@@ -199,6 +199,16 @@ cluster ingress IP):
| `docs.leeworks.dev` | `<cluster ingress IP>` | | `docs.leeworks.dev` | `<cluster ingress IP>` |
| `grafana.leeworks.dev` | `<cluster ingress IP>` | | `grafana.leeworks.dev` | `<cluster ingress IP>` |
| `status.leeworks.dev` | `<cluster ingress IP>` | | `status.leeworks.dev` | `<cluster ingress IP>` |
| `registry.leeworks.dev` | `<cluster ingress IP>` |
Verify DNS propagation:
```bash
for host in zip holidays aqi docs grafana status registry; do
echo -n "${host}.leeworks.dev: "
dig ${host}.leeworks.dev +short
done
```
cert-manager will obtain Let's Encrypt certificates automatically once DNS cert-manager will obtain Let's Encrypt certificates automatically once DNS
propagates (typically minutes, up to 48 h). propagates (typically minutes, up to 48 h).