docs: record active tunnel and public hello
infra-ci / manifests (push) Failing after 3s
infra-ci / manifests (pull_request) Failing after 4s

This commit is contained in:
Noel Sabia committed 2026-11-14 06:51:06 +01:00
1 parent eed7e62aa7
commit 40bc8e47d0
2 files changed
+18 -17

No files matched your search

+13 -12
View File
@@ -24,20 +24,21 @@ Gate 1 passes only when **all** of these are true:
Do not claim Gate 1 from a local `kubectl port-forward`, a green manifest
dry-run, or a container that only runs on your laptop.
## Current external status (2026-11-14 ~06:40 CET)
## Current external status (2026-11-14 ~06:50 CET)
Re-check before trusting this snapshot:
- **Verified:** cluster access, scheduling, Service DNS/HTTP, probes, Secrets,
non-root + read-only-root + `emptyDir`, and egress to Cloudflare,
Open-Meteo, and `git.noelsabia.dev`.
- **Tunnel created, connector pending:** `pulsecast-gate1` has routes for
`pulse.noelsabia.dev` and `api-pulse.noelsabia.dev`; it stays Inactive until
the `cloudflared` Deployment runs.
- **Tunnel active:** `pulsecast-gate1` has routes for `pulse.noelsabia.dev`
and `api-pulse.noelsabia.dev`; `cloudflared` is `1/1` with four HTTP/2
connections, and `https://pulse.noelsabia.dev` returns 200 from hello with
valid TLS. `api-pulse` returns 502 until the API is deployed.
- **DNS works:** public resolvers return Cloudflare IPs for
`pulse.noelsabia.dev` and the old `api.pulse.noelsabia.dev`. A local
`systemd-resolved` NXDOMAIN cache can be flushed with
`resolvectl flush-caches`.
`pulse.noelsabia.dev` and `api-pulse.noelsabia.dev`. A local
`systemd-resolved` negative cache can be cleared with
`resolvectl query --cache=no NAME` followed by `resolvectl flush-caches`.
- **API hostname is `api-pulse.noelsabia.dev`:** Universal SSL covers only
`*.noelsabia.dev`; a two-level `api.pulse.noelsabia.dev` is not covered by
that certificate.
@@ -51,10 +52,10 @@ Re-check before trusting this snapshot:
- **Numeric UIDs are required:** a non-numeric image user breaks
`runAsNonRoot` on SKE (reproduced with `curlimages/curl`). Every pod in
`deploy/k8s/` sets explicit numeric `runAsUser`/`runAsGroup`/`fsGroup`.
- **Repo status (2026-11-14 ~05:10 UTC):** all three images now build and pass
- **Repo status (2026-11-14 ~06:50 CET):** all three images build and pass
local manifest-equivalent runtime checks (numeric UID, read-only root, `/tmp`
tmpfs). There is no remaining Dockerfile blocker; the human Gitea/Tunnel
steps are what remain.
tmpfs). Remaining steps are the image push, `control-auth`, deploy, and
public smoke.
## What is possible now vs what is blocked
@@ -62,8 +63,8 @@ Re-check before trusting this snapshot:
|---|---|---|
| Read-only cluster/manifest check | agent or human | **ready now** (`make gate1-check`) |
| Gitea push login + hello-world push | human | **done**; hello pull and Service verified |
| `gitea-regcred`, `cloudflared`, `control-auth` Secrets | human | `gitea-regcred` **done**; `cloudflared`/`control-auth` pending |
| Cloudflare Tunnel + public hostnames/DNS | human | tunnel created; routes added; **connector pending** |
| `gitea-regcred`, `cloudflared`, `control-auth` Secrets | human | `gitea-regcred` + `cloudflared` **done**; `control-auth` pending |
| Cloudflare Tunnel + public hostnames/DNS | human | **done**; tunnel active, public hello 200 |
| `api` image | human | **ready** — `make build-api` + manifest-equivalent run verified locally |
| `ml` image | human | **ready** — `make build-ml` + manifest-equivalent run verified locally |
| `web` image | human | **ready** — `make build-web` + manifest-equivalent run verified locally |