Files
infrastructure/servers/legion/apps/neuron-web.yaml
Will Anderson 3daf615dd2 add neuron-web phase-1 deploy on Legion
Stand up the elb-built native El landing server on Legion k3s alongside
the existing Cloud Run prod marketing site. Image is built on
gitea-runner-1 from elb-emitted .c files + native cc and pushed to
registry.neuralplatform.ai/neuron-web:dev-dfe41234. Deployment exposes
web-stage.neuralplatform.ai via Traefik + Cloudflare tunnel.

The point is to have a working local instance we can iterate against
while we redesign the CI/CD pipeline; nothing here replaces the Cloud
Run deploy yet.

* k8s/neuron-technologies/web/ — namespace, deployment, service, ingress,
  registry-pull-secret + externalsecret pulling anthropic/supabase keys
  from Vault
* apps/neuron-web.yaml — Argo CD Application
* dns-neuralplatform.tf, main.tf — CNAME + tunnel ingress for
  web-stage.neuralplatform.ai
2026-05-03 10:45:18 -05:00

27 lines
807 B
YAML

# neuron-web — El landing page server (Phase 1 deploy on Legion)
#
# Sibling to neuron-marketing (Next.js prod) and neuron-stage (Next.js stage).
# This deployment runs the elb-built native El binary at
# web-stage.neuralplatform.ai. Coexists with the Cloud Run prod marketing
# site; nothing here replaces that yet.
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: neuron-web
namespace: argocd
spec:
project: default
source:
repoURL: http://gitea.git.svc.cluster.local:3000/will/infrastructure.git
targetRevision: main
path: servers/legion/k8s/neuron-technologies/web
destination:
server: https://kubernetes.default.svc
namespace: neuron-web
syncPolicy:
automated:
prune: true
selfHeal: true
syncOptions:
- CreateNamespace=true