From da4ebdfcaf19f903dd6b257feb7e00feace8fd47 Mon Sep 17 00:00:00 2001 From: kfox1111 Date: Fri, 3 May 2024 14:17:31 -0700 Subject: [PATCH] Fix federation certificate name when upstream enabled (#347) When both federation certificates and upstream authority both use cert-manager, there is a naming conflict. Signed-off-by: Kevin Fox --- .../charts/spire-server/templates/federation-certificate.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charts/spire/charts/spire-server/templates/federation-certificate.yaml b/charts/spire/charts/spire-server/templates/federation-certificate.yaml index 013d302..a4329d7 100644 --- a/charts/spire/charts/spire-server/templates/federation-certificate.yaml +++ b/charts/spire/charts/spire-server/templates/federation-certificate.yaml @@ -20,7 +20,7 @@ secretName: {{ $issuerFullName }}-cert apiVersion: cert-manager.io/v1 kind: Certificate metadata: - name: {{ include "spire-server.fullname" . }} + name: {{ include "spire-server.fullname" . }}-fed namespace: {{ include "spire-server.namespace" . }} spec: {{ merge (include "spire-server.federation-cert-manager-default-cert" . | fromYaml) .Values.federation.tls.certManager.certificate | toYaml | nindent 2 }}