From 0c79aea82fb05670bfe8e8c322e064a64c9fd625 Mon Sep 17 00:00:00 2001
From: Mayne0213 <bluemayne0213@icloud.com>
Date: Sun, 28 Dec 2025 16:46:43 +0900
Subject: [PATCH] FIX(cert-manager): cert-manager

- to use haproxy ingress class
Changed from nginx to haproxy to match the current ingress controller.
This resolves the ArgoCD sync loop in cluster-infrastructure.
---
 cert-manager/cluster-issuer-prod.yaml    | 4 ++--
 cert-manager/cluster-issuer-staging.yaml | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/cert-manager/cluster-issuer-prod.yaml b/cert-manager/cluster-issuer-prod.yaml
index e6c4886..97defaf 100644
--- a/cert-manager/cluster-issuer-prod.yaml
+++ b/cert-manager/cluster-issuer-prod.yaml
@@ -17,8 +17,8 @@ spec:
       name: letsencrypt-prod
 
     # HTTP-01 challenge를 사용하여 도메인 소유권 검증
-    # Nginx Ingress를 통해 /.well-known/acme-challenge/ 경로로 검증
+    # HAProxy Ingress를 통해 /.well-known/acme-challenge/ 경로로 검증
     solvers:
     - http01:
         ingress:
-          class: nginx
+          class: haproxy
diff --git a/cert-manager/cluster-issuer-staging.yaml b/cert-manager/cluster-issuer-staging.yaml
index f49a0a3..51e8452 100644
--- a/cert-manager/cluster-issuer-staging.yaml
+++ b/cert-manager/cluster-issuer-staging.yaml
@@ -19,4 +19,4 @@ spec:
     solvers:
     - http01:
         ingress:
-          class: nginx
+          class: haproxy