fix: use certificate-safe api-pulse hostname
Cloudflare Universal SSL covers *.noelsabia.dev only one level deep. api.pulse.noelsabia.dev is two levels and fails the certificate check. - switch the API base/SSE URLs to api-pulse.noelsabia.dev - update smoke, k6, runbook, and failure drills - record the verified DNS/certificate diagnosis and local cache flush
This commit is contained in:
1 parent
2eacb62696
commit
e8e0f2035b
10 files changed
+68
-55
No files matched your search
@@ -51,8 +51,11 @@ hostname, and verification steps.
|
||||
(read-only root, `/tmp` tmpfs, numeric UID). There is no Dockerfile blocker.
|
||||
- Gitea pull is proven: `gitea-regcred` exists and the hello pod pulled from
|
||||
`git.noelsabia.dev/noel/hello:gate1`; the Service returned HTTP 200.
|
||||
- Still human-only: Cloudflare Tunnel + DNS hostnames, `cloudflared` and
|
||||
`control-auth` Secrets, then image push/deploy/smoke.
|
||||
- Tunnel `pulsecast-gate1` is created with `pulse` and `api-pulse` routes; the
|
||||
connector is pending. The API hostname is `api-pulse.noelsabia.dev` because
|
||||
Universal SSL only covers `*.noelsabia.dev`.
|
||||
- Still needed: `cloudflared`/`control-auth` Secrets, image push, deploy, and
|
||||
public smoke.
|
||||
|
||||
## CI
|
||||
|
||||
|
||||
Reference in new issue
Block a user