FEAT(grafana): add per-application ingress

- management for Grafana
- Added ingress.yaml for Grafana
- Updated kustomization file to include ingress resource
- Migrated from centralized ingress management to per-app architecture
This commit is contained in:
2025-12-25 20:21:28 +09:00
parent a04fff40a3
commit 7d41461e2e
2 changed files with 41 additions and 0 deletions

40
grafana/ingress.yaml Normal file
View File

@@ -0,0 +1,40 @@
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: grafana-ingress
namespace: monitoring
annotations:
nginx.ingress.kubernetes.io/rewrite-target: /
# HTTP를 HTTPS로 자동 리다이렉트
nginx.ingress.kubernetes.io/ssl-redirect: "true"
# cert-manager가 인증서를 자동으로 발급하도록 설정
cert-manager.io/cluster-issuer: "letsencrypt-prod"
spec:
ingressClassName: haproxy
# TLS 설정
tls:
- hosts:
- grafana0213.kro.kr
- www.grafana0213.kro.kr
secretName: grafana-tls
rules:
- host: grafana0213.kro.kr
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: grafana
port:
number: 80
- host: www.grafana0213.kro.kr
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: grafana
port:
number: 80

View File

@@ -5,3 +5,4 @@ resources:
# ArgoCD Application 리소스는 infrastructure/kustomization.yaml에서 관리
# - argocd/grafana.yaml
- vault/grafana-admin-password.yaml
- ingress.yaml