Skip to content

Conversation

@Smana
Copy link

@Smana Smana commented Nov 25, 2025

📑 Description

Add namespace: {{ include "keep.namespace" . }} to all Kubernetes resource templates that were missing it. This ensures proper namespace handling when deploying via tools like kustomize that rely on namespace being explicitly set in resource metadata.

Resources updated:

  • ServiceAccount
  • Deployments (backend, frontend, websocket, database)
  • Services (backend, frontend, websocket, database)
  • HorizontalPodAutoscalers
  • Secrets and ConfigMaps
  • PersistentVolumeClaim
  • CronJob (db-cleanup)
  • Job (delete-secret)
  • Ingresses (nginx, haproxy, traefik)
  • Routes (OpenShift)

Also updated GKE BackendConfig and Traefik Middleware templates to use the keep.namespace helper instead of .Release.Namespace for consistency.

Note: PersistentVolume (db-pv.yaml) is intentionally excluded as it is a cluster-scoped resource that does not have a namespace.

✅ Checks

  • My pull request adheres to the code style of this project
  • All the tests have passed

Add `namespace: {{ include "keep.namespace" . }}` to all Kubernetes
resource templates that were missing it. This ensures proper namespace
handling when deploying via tools like kustomize that rely on namespace
being explicitly set in resource metadata.

Resources updated:
- ServiceAccount
- Deployments (backend, frontend, websocket, database)
- Services (backend, frontend, websocket, database)
- HorizontalPodAutoscalers
- Secrets and ConfigMaps
- PersistentVolumeClaim
- CronJob (db-cleanup)
- Job (delete-secret)
- Ingresses (nginx, haproxy, traefik)
- Routes (OpenShift)

Also updated GKE BackendConfig and Traefik Middleware templates to use
the `keep.namespace` helper instead of `.Release.Namespace` for
consistency.

Note: PersistentVolume (db-pv.yaml) is intentionally excluded as it is
a cluster-scoped resource that does not have a namespace.
@Smana Smana requested a review from talboren as a code owner November 25, 2025 16:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant