unrip/deploy/k8s/base/kustomization.yaml
philipp 551050beb3
All checks were successful
deploy / deploy (push) Successful in 46s
Add internal ntfy utility service
Proof: npm test; PYTHONPATH=. python3 test/render_release_manifest_test.py; PYTHONPATH=. python3 test/repo_deployments_test.py; PYTHONPATH=. python3 test/ntfy_manifest_test.py; kubectl kustomize deploy/k8s/base.

Assumptions: ntfy should start as an internal ClusterIP utility so repo-owned services can publish without exposing an unauthenticated public notification endpoint; mobile delivery needs a separate authenticated ingress or external endpoint decision.

Still fake: No public ntfy ingress or operator mobile subscription exists yet; no existing runtime path emits ntfy notifications by default; ntfy cache storage is ephemeral emptyDir.
2026-04-15 21:23:41 +02:00

10 lines
209 B
YAML

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- namespace.yaml
- utility-namespace.yaml
- ntfy.yaml
- redpanda.yaml
- postgres.yaml
- unrip.yaml
- bootstrap-job.yaml