1b629d8ea3
This StatefulSet was deployed manually outside git at some point before this repo's GitOps work began, and was destroyed when deleting the core Kustomization triggered a full namespace recreation (Flux prune-on-delete cascades regardless of kubectl's --cascade flag - that only affects Kubernetes' own owner-reference GC, not Flux's finalizer). Reconstructed from its own logs (NATS_STREAM=NOTIFICATIONS, NATS_CONSUMER=notifications-worker, FILTER_SUBJECT=api.v1.notifications.push) plus the same pattern as its sibling workers. Resource limits and WORKER_CONCURRENCY are a best-guess match to worker-rider-logs, since the original values were never version-controlled anywhere. Adding it to git now so this can't happen again. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
23 lines
910 B
YAML
23 lines
910 B
YAML
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
|
|
# No top-level `namespace:` override - every resource below (including
|
|
# ingress-unified.yaml, which spans alaska and nearle) already sets its own
|
|
# metadata.namespace explicitly. A blanket override here would silently
|
|
# force cross-namespace resources into "core" and break their backend refs.
|
|
|
|
resources:
|
|
- core-namespace.yaml
|
|
- core-secrets.yaml
|
|
- core-config.yaml
|
|
- worker-script.yaml
|
|
- workers.yaml
|
|
- worker-notifications.yaml
|
|
- worker-pdb.yaml
|
|
- ingress-unified.yaml
|
|
# traefik-middlewares.yaml intentionally excluded - this cluster's
|
|
# Traefik has no Middleware CRD installed under any API group, so this
|
|
# can never apply. The router.middlewares annotation referencing it on
|
|
# the Ingress has been a pre-existing no-op; actual CORS handling comes
|
|
# from nginx-queue-proxy.conf and the apps' own CORS middleware.
|