Files
zero-scale-platform/deploy/kustomization.yaml
claude e33abed59b Add QA and feature-branch environments
env create/delete/gc/list manage a namespace per environment, labelled
zero-scale.io/env, with a ResourceQuota, its own gateway and an optional
wildcard route. A zero-scale-env ConfigMap records the env and may override
the platform's database clusters. Hosts use ${ENV_SUFFIX}; databases in a
non-primary env are named db_<env>_<app>_<hash> and carry an owner comment,
so env delete drops only what the env owns. oauth-setup --auth-host serves
every app's login from one callback host. deploy/ manifests no longer
hardcode a namespace; deploy/kustomization.yaml sets it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016uKdmp7tLySXvQXALz2x9V
2026-10-27 06:44:55 -04:00

26 lines
828 B
YAML

# Core gateway resources for one namespace. Pick the namespace here (or with
# 'kustomize edit set namespace qa') and apply with: kubectl apply -k deploy/
# The RoleBinding subject follows the namespace automatically.
#
# 'zero-scale-ctl gateway install' and 'zero-scale-ctl env create' render an HA
# version of these (replicas, PDB, spread) and are the recommended path.
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: default
resources:
- rbac.yaml
- pvc.yaml
- deployment.yaml
- service.yaml
replacements:
- source:
kind: ServiceAccount
name: zero-scale-gateway
fieldPath: metadata.namespace
targets:
- select:
kind: RoleBinding
name: zero-scale-gateway-binding
fieldPaths:
- subjects.[name=zero-scale-gateway].namespace