riotpiao-poimen/homelab-frontend
2
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
90 Commits 2 Branches 2 Tags
5dd76f3b49ff2a4247ece4a97128050fb0194f53
Commit Graph
7 Commits
Author SHA1 Message Date
Admin Bot c87463c850 fix(s3): correct MinIO service port and allow egress
CI / CI (pull_request) Successful in 3m16s
Details 
MinIO ClusterIP service listens on port 80 (targetPort 9000).
Config had port 9000 which caused 30s timeout then 502 — gateway
connected to service port 9000 which doesn't exist on the ClusterIP.

Changes:
- configmap.yaml: S3 upstream :9000 → :80
- gateway-config-secret.enc.yaml: same
- network-policy.yaml: add port 80 egress to storage namespace

Verified: S3 adapter now reaches MinIO (403 AccessDenied = auth issue,
not connectivity).
 2026-09-08 09:58:36 -07:00
Admin Bot a55e4c7b43 fix: use pod ports (9000/9443) for authentik egress, not service ports
CI / Vet, test, build (push) Successful in 4m3s
Details
CI / Build and push image (push) Successful in 1m31s
Details
2026-09-04 19:09:43 -07:00
Admin Bot d998d7e63c fix: add egress rules for iam, sqs, temporal, poimen, storage namespaces
CI / Build and push image (push) Canceled after 0s
Details
CI / Vet, test, build (push) Canceled after 2m47s
Details
2026-09-04 19:06:50 -07:00
Admin Bot 8ba4e0facc fix: allow portfolio namespace to reach api-gateway for LLM chat
CI / Vet, test, build (push) Successful in 3m52s
Details
CI / Build and push image (push) Successful in 1m17s
Details
2026-09-01 11:15:23 -07:00
Admin Bot de34a6c8cc fix(network): allow poimen namespace to access api-gateway
CI / Vet, test, build (push) Canceled after 2m38s
Details
CI / Build and push image (push) Canceled after 0s
Details 
Enable Poimen orchestrator and worker pods to reach the LLM API gateway
in the api namespace.

The api-gateway NetworkPolicy was only allowing traffic from:
- ingress-nginx (external ingress)
- monitoring (Prometheus scraping)

Added new ingress rule to allow:
- poimen namespace (orchestrator-job and worker pods)
- Port 8080 (api-gateway service port)

This fixes the DNS resolution error where orchestrator pods couldn't
reach http://api-gateway.api:8080/health from within the cluster.

Managed via ArgoCD in homelab/k8s/argocd/apps/55-api-gateway.yaml
which syncs from this repo's k8s/ directory.
 2026-08-31 14:59:29 -07:00
Story Crater Bot 500eb74577 fix: match namespaces by kubernetes.io/metadata.name in netpol egress 
kube-system and llm-serving carry only the automatic label, so DNS and
upstream egress matched nothing and every dispatch failed with 502.
 2026-08-20 00:04:17 -07:00
Story Crater BotandClaude Opus 5 058f11cf2b chore: initial commit of Go API gateway
CI / Test (push) Canceled after 0s
Details
CI / Vet (push) Canceled after 0s
Details
CI / Build (push) Canceled after 0s
Details
CI / Security (govulncheck) (push) Canceled after 0s
Details 
Baseline for the Kong replacement on api.riotpiao.com. Brings the working
tree under version control for the first time: gateway source, the task
board that drives the agent runs, test fixtures, and K8s manifests.

Anchor the gateway ignore rule to the repo root. Unanchored, "gateway"
also matched the cmd/gateway/ source directory, so the program entrypoint
was excluded from every commit.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
 2026-08-19 20:54:34 -07:00