https://ops.docs.72602.space/installation/proxy/index.html Open WebUI Ollama Moderation Gateway Install (ArgoCD) Sub2API Backup & Restore Install (ArgoCD) Ops Hugo en Tue, 12 May 2026 15:00:59 +0800 https://ops.docs.72602.space/installation/proxy/openwebui/index.html Tue, 12 May 2026 15:00:59 +0800 https://ops.docs.72602.space/installation/proxy/openwebui/index.html Archived The 72602 OpenWebUI deployment is retired and has no current installation route. argocd/open-webui does not exist, and the ai namespace has no OpenWebUI resources. txt2img.agent.72602.online is retired and has no working endpoint; its DNS record, certificate, TLS Secret, and unreferenced data claims were removed. The repository file manifests/application/open-webui.yaml is a historical, non-deployed manifest. It is not consumed by the current GitOps setup and still points to the retired route. Do not use it as an installation source. https://ops.docs.72602.space/installation/proxy/ollamamoderationgateway/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://ops.docs.72602.space/installation/proxy/ollamamoderationgateway/index.html Overview The Ollama Moderation Gateway provides an OpenAI-compatible moderation endpoint backed by Ollama models. It is deployed via the 72602 ArgoCD GitOps pipeline using the Helm chart ollama-moderation-gateway (version 0.1.0). ArgoCD Application: argocd/ollama-moderation-gateway (child of argocd/ops-docs) Namespace: moderation Service: ollama-moderation-gateway (port 8000) Ingress: moderation.llm.72602.space (TLS via cert-manager) Current Operational State: Deployment ollama-moderation-gateway desired replicas: 3, available replicas: 3. Service reports three Ready endpoints. Single-node resource metrics are healthy. The image, runtime configuration and Ingress remain unchanged; only replicaCount was changed. https://ops.docs.72602.space/installation/proxy/sub2api/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://ops.docs.72602.space/installation/proxy/sub2api/index.html Web Page sub2api web page (https://token.72602.space) Current State Git owner: argocd/ops-docs, source https://github.com/AaronYang0628/docs.git, path manifests ArgoCD Application: argocd/sub2api Namespace: application OCI chart: ghcr.io/aaronyang0628/helm-chart-mirror/sub2api (0.1.18) Application image: ghcr.io/wei-shaw/sub2api@sha256:996a0ea43500550f233a2f653de58dcd77f42d3e244805894fcccdd32b612147 Public API and OAuth host: token.72602.space Ingress class: nginx TLS certificate: token.72602.space-tls (Ready) External PostgreSQL: postgresql.database.svc.cluster.local:5432 (database/user: sub2api) Application PVC: sub2api-data, 10Gi, local-path, RWO Redis PVC: 8Gi, local-path, RWO; AOF is enabled RollingUpdate: maxUnavailable: 0, maxSurge: 1 Google OAuth Route Use the 72602 public URL: https://token.72602.space. Google OAuth is enabled in the live application. The start endpoint is /api/v1/auth/oauth/google/start and the callback URI generated by the running application is: https://token.72602.space/api/v1/auth/oauth/google/callback. The application sets the OAuth state, redirect, and provider cookies with HttpOnly, Secure, SameSite=Lax, and Path=/api/v1/auth/oauth. The frontend callback page is /auth/oauth/callback. The Pod requires the cluster egress proxy for Google token exchange. The GitOps source sets HTTP_PROXY and HTTPS_PROXY to http://192.168.0.25:17890 and bypasses that proxy for cluster-local ranges. sub2api.home.geekcity.tech:32443 is a separate external endpoint, not the 72602 ingress. It returns 404 for the 72602 OAuth start path and must not be used for this login flow. If Google reports a redirect URI mismatch, register only the exact callback URI above in the Google OAuth client. Google Cloud Console changes are not managed by this Kubernetes repository. Docs Backup & RestoreSub2API pre-upgrade backup and recovery runbook