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
17 lines
545 B
YAML
17 lines
545 B
YAML
apiVersion: v1
|
|
kind: PersistentVolumeClaim
|
|
metadata:
|
|
name: zero-scale-binaries-pvc
|
|
labels:
|
|
app.kubernetes.io/name: zero-scale-gateway
|
|
app.kubernetes.io/part-of: zero-scale-platform
|
|
spec:
|
|
accessModes:
|
|
- ReadWriteMany
|
|
# Note: ReadWriteMany (RWX) is recommended so multiple pod replicas can mount /opt/apps.
|
|
# If your cluster does not provide an RWX StorageClass, change accessModes to ReadWriteOnce.
|
|
resources:
|
|
requests:
|
|
storage: 5Gi
|
|
# storageClassName: "" # Leave commented to use cluster default StorageClass
|