From aa2730efd57adffd5bcc4e9236e045b944d1850b Mon Sep 17 00:00:00 2001 From: Peter Parker Date: Fri, 14 Aug 2026 00:16:06 -0500 Subject: [PATCH] fix: OpenViking ingress TLS issuer from letsencrypt-internal to letsencrypt-prod The letsencrypt-internal ClusterIssuer does not exist on the cluster. Only letsencrypt-prod and letsencrypt-staging are available. Both use DNS-01 via Cloudflare for the mk-labs.cloud zone, so they work for internal-only hosts with no public HTTP reachability. Fixes: https://github.com/volcengine/openviking/issues/... Closes: kanban task t_1c2cc2db --- cluster/platform/openviking/values.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cluster/platform/openviking/values.yaml b/cluster/platform/openviking/values.yaml index 89055ee..3d474c0 100644 --- a/cluster/platform/openviking/values.yaml +++ b/cluster/platform/openviking/values.yaml @@ -53,8 +53,8 @@ ingress: enabled: true className: nginx annotations: - # Internal cert-manager cluster issuer (self-signed or internal CA) - cert-manager.io/cluster-issuer: "letsencrypt-internal" + # Internal cert-manager cluster issuer (DNS-01 via Cloudflare) + cert-manager.io/cluster-issuer: "letsencrypt-prod" # Block external DNS registration (internal only) external-dns.alpha.kubernetes.io/enabled: "false" hosts: