1b38a0c240
kubectl api-resources shows no Middleware kind under any API group, so this manifest could never apply and was blocking the entire core Kustomization. The Ingress annotation referencing it has been a pre-existing no-op; CORS is actually handled by nginx-queue-proxy.conf and each app's own CORS middleware. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
22 lines
880 B
YAML
22 lines
880 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-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.
|