prole/deploy/opentofu/k3s/manifests/knoe/kong-service.yaml
chrisfu 82c1ff555f fix(k3d): rename prole-svc-kong → knoe-svc-kong, clean up stale resources
k3s manifests still used prole-svc-kong after the rebrand; init_kong.sh
was waiting on `rollout status deployment/knoe-svc-kong` which never
existed, hanging the Common Services milestone.

- Rename kong-deployment.yaml and kong-service.yaml: prole-svc-kong →
  knoe-svc-kong (labels, selector, configmap volume ref)
- Remove prole-svc-kong-configmap.yaml (static file replaced by
  init_kong.sh dynamic ConfigMap generation; hardcoded namespace and
  prole-branded routes were dead weight)
- init_kong.sh: add cleanup_legacy_prole_kong() called from action_update()
  to remove stale prole-era resources before deploying knoe-svc-kong
- init_kong.sh: add _is_host_claimed_by_other_ingress() helper; set
  include_gitea_host=0 for k3d mode (git is port-forward only, no public
  hostname) — keeps the safety-net pre-check for k3s
- actions.py: extend legacy namespace dedupe to sweep prole-svc-kong from
  both default and service_ns

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-03 00:24:02 -07:00

23 lines
400 B
YAML

apiVersion: v1
kind: Service
metadata:
name: knoe-svc-kong
annotations:
argocd.argoproj.io/sync-wave: "1"
labels:
app: knoe-svc-kong
spec:
selector:
app: knoe-svc-kong
ports:
- name: proxy
port: 8000
targetPort: proxy
- name: admin
port: 8001
targetPort: admin
- name: ssh-proxy
port: 3022
targetPort: ssh-proxy
type: ClusterIP