homelab/manifests/home-services/alert-bridge-ingress.yaml
Nik Afiq 85cc8494fa
Some checks failed
validate / lint (push) Failing after 1s
feat: add alert bridge service and related configurations
2026-08-01 22:51:59 +09:00

40 lines
1.3 KiB
YAML

# Apply: kubectl apply -f manifests/home-services/alert-bridge-ingress.yaml
# Delete: kubectl delete -f manifests/home-services/alert-bridge-ingress.yaml
# Description: Internal-CA TLS certificate and Traefik IngressRoute for
# alert-bridge at alert-bridge.home.arpa, so a caller elsewhere on the home
# network (not inside the k8s cluster, e.g. a cronjob on another LAN host) can
# reach POST /alerts. Modeled on manifests/authentik/authentik-ingress.yaml's
# shape (internal-ca-issuer + websecure entrypoint) rather than
# alexa-bridge-public-ingress.yaml's letsencrypt-prod pattern, since this is
# not exposed to the public internet - LAN-only, same trust tier as Argo CD,
# Traefik's own dashboard, etc.
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
name: alert-bridge-tls
namespace: home-services
spec:
secretName: alert-bridge-tls
issuerRef:
name: internal-ca-issuer
kind: ClusterIssuer
dnsNames:
- alert-bridge.home.arpa
---
apiVersion: traefik.io/v1alpha1
kind: IngressRoute
metadata:
name: alert-bridge
namespace: home-services
spec:
entryPoints:
- websecure
routes:
- match: Host(`alert-bridge.home.arpa`)
kind: Rule
services:
- name: alert-bridge
port: 8080
tls:
secretName: alert-bridge-tls