Skip to content

Add internal gateway cert SANs only for ca issuer - #1381

Merged
ArnobKumarSaha merged 1 commit into
masterfrom
arnob-gw-cert-sans
Oct 28, 2026
Merged

ArnobKumarSaha merged 1 commit into
masterfrom
arnob-gw-cert-sans

Conversation

@ArnobKumarSaha

Copy link
Copy Markdown
Member

service-gateway's <tenant>-gw Certificate always included cluster-internal SANs (prom-label-proxy*, otel-nats*, *.otel-nats*, otel-forwarder*), whatever infra.tls.issuer was set to.

With issuer: letsencrypt (or letsencrypt-staging), the ACME server rejects the entire order:

urn:ietf:params:acme:error:rejectedIdentifier: Invalid identifiers requested ::
Cannot issue for "*.otel-nats": Domain name does not end with a valid public suffix (TLD)

The Certificate then never becomes Ready, so the gateway HelmRelease hangs in Running 'upgrade' action until it times out, and retries forever because remediation retries are -1. That in turn blocks kubeops/ace (dependsOn gateway) and the ace-upgrader job.

This change adds the internal SANs only when infra.tls.issuer is ca.

Rendered dnsNames with hostType=domain:

  • letsencrypt: ops.appscode.dev only
  • ca: unchanged (public host + all internal SANs)

ACME issuers reject cluster-internal names like prom-label-proxy and
otel-nats.<ns>.svc, which fails the whole order and leaves the gateway
HelmRelease waiting on a Certificate that never becomes Ready.

Signed-off-by: Arnob kumar saha <arnob@appscode.com>
@ArnobKumarSaha
ArnobKumarSaha merged commit df3278c into master Oct 28, 2026
7 checks passed
@ArnobKumarSaha
ArnobKumarSaha deleted the arnob-gw-cert-sans branch October 28, 2026 11:31
ArnobKumarSaha added a commit that referenced this pull request Oct 28, 2026
Signed-off-by: Arnob kumar saha <arnob@appscode.com>
ArnobKumarSaha added a commit that referenced this pull request Oct 29, 2026
Signed-off-by: Arnob kumar saha <arnob@appscode.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant