Files
OKF_Vault/mission/friday-blockers.md
T
2026-11-13 20:14:32 +01:00

4.0 KiB

Access verification — what the kubeconfig allows

Verified on 2026-11-13 ~20:15 against fch26-onemanarmy-sa-kubeconfig.yaml.

Verdict

The kubeconfig is enough to deploy workloads, but not enough to expose them with an Ingress and not enough to run Jobs/CronJobs.

Use Cloudflare Tunnel for HTTPS/domain. Use a build-time batch for ML. Do not plan on Ingress, cert-manager, external-dns or Jobs.

Permissions

Can create Cannot create
Deployments, Services, ConfigMaps, Secrets, ServiceAccounts, Pods, PVCs Ingress, Jobs, CronJobs, NetworkPolicies, Roles, RoleBindings

Also:

  • No cert-manager CRDs, no Gateway API, no IngressClass visibility.
  • No ResourceQuota or LimitRange — three small pods fit.
  • No explicit Pod Security Admission labels; a non-root nginx-unprivileged pod ran successfully.
  • Public image pull works (Docker Hub, 2.8 s).
  • The namespace is fch26-onemanarmy; context fch26-onemanarmy-sa-context.

What this means for the architecture

Need Path
Public HTTPS URL Cloudflare Tunnel (cloudflared Deployment), not Ingress.
TLS certificate Cloudflare edge; no cert-manager.
DNS Cloudflare Tunnel public hostnames; no external-dns.
Batch training Build-time pipeline; no Job/CronJob in this namespace.
Registry Gitea git.noelsabia.dev with imagePullSecret; public Docker Hub also works.
Pod-to-pod traffic Test web → api → ml after deployment. You cannot create NetworkPolicies; if a default-deny exists, escalate.

Security — act on this

The kubeconfig contains a service account bearer token and was shared in chat. Treat it as compromised.

  • Token expiry: 2026-11-23 19:49 CET — valid through the hackathon.
  • The file is git-ignored and chmod 600.
  • Rotate/revoke the token after the event, or ask the organizers for a new kubeconfig if you want to rotate before Sunday.
  • Never paste the token into chat, a commit, a slide, or a screenshot.
  • Create a separate read-only Gitea package token for the cluster pull; do not reuse your admin token.

Remaining blockers / next actions

  1. Gitea image pull

    • Create a read-only package token.
    • docker login git.noelsabia.dev, push a hello-world.
    • Create gitea-regcred in fch26-onemanarmy.
    • Deploy the hello-world and verify it runs.
  2. Cloudflare Tunnel

    • Create a tunnel in Cloudflare Zero Trust.
    • Add public hostnames:
      • pulse.noelsabia.dev → http://web:3000
      • api.pulse.noelsabia.dev → http://api:8080
    • Create the cloudflared Secret with the tunnel token.
    • Deploy cloudflare/cloudflared and verify both URLs over HTTPS.
  3. Connectivity

    • Deploy web/api/ml with ClusterIP Services.
    • Test api → ml and web → api from inside the namespace.
    • If a default-deny NetworkPolicy blocks traffic, escalate; you cannot create one.
  4. SSE

    • Test EventSource through Cloudflare with the 15 s heartbeat.
    • If buffered, use the frontend polling fallback.
  5. Product/data clarifications

    • Q6: use only the provided CSV, or allow Open-Meteo weather/holidays?
    • Q7: basic auth on /control only, or the whole app?
    • Q9: paper format (Markdown → PDF is fine).

Mentor questions — minimum

  1. What Pod Security Admission level applies to fch26-onemanarmy?
  2. Is there a default-deny NetworkPolicy in the namespace?
  3. Is outbound 443 to Cloudflare allowed for cloudflared? (Image pull works, so egress exists.)
  4. Is there any restriction on running cloudflared or using Cloudflare Tunnel?
  5. If we need a runtime batch job, can the namespace be granted create jobs / create cronjobs? If not, build-time is fine.

Done when

  • Gitea hello-world runs in the namespace.
  • https://pulse.noelsabia.dev and https://api.pulse.noelsabia.dev/api/healthz respond.
  • web → api → ml connectivity verified.
  • SSE event arrives on a phone through Cloudflare.
  • Token rotation plan is noted for after the event.