When adding something like a common-name to a certificate <div class="snippet-clip

tls and extraTls about sealed-secrets HOT 2 OPEN

cdenneen commented on July 22, 2024 2

tls and extraTls

from sealed-secrets.

Comments (2)

cdenneen commented on July 22, 2024

Work around for now was to create a Certificate myself and use the following values (removed tls: true and the annotations):

    ingress:
      enabled: true
      ingressClassName: nginx
      hostname: sealed-secrets.kustomize-me.clusters.aws.platform.example.com
      extraHosts:
        - name: sealed-secrets.platform.example.com
      extraTls:
        - hosts:
            - sealed-secrets.platform.example.com
            - sealed-secrets.kustomize-me.clusters.aws.platform.example.com
          secretName: sealed-secrets-tls

---
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: sealed-secrets
  namespace: kube-system
spec:
  commonName: sealed-secrets.platform.example.com
  dnsNames:
    - sealed-secrets.platform.example.com
    - sealed-secrets.kustomize-me.clusters.aws.platform.example.com
  secretName: sealed-secrets-tls
  privateKey:
    rotationPolicy: Always
  issuerRef:
    kind: ClusterIssuer
    name: letsencrypt

from sealed-secrets.

cdenneen commented on July 22, 2024

Actually to avoid having to setup a Certificate resource directly I was able to use cert-manager annotation just had to keep tls: false and only use extraTls:

    ingress:
      enabled: true
      ingressClassName: nginx
      annotations:
        cert-manager.io/cluster-issuer: letsencrypt
        cert-manager.io/common-name: sealed-secrets.platform.example.com
      hostname: sealed-secrets.kustomize-me.clusters.aws.platform.example.com
      extraHosts:
        - name: sealed-secrets.platform.example.com
      extraTls:
        - hosts:
            - sealed-secrets.platform.example.com
            - sealed-secrets.kustomize-me.clusters.aws.platform.example.com
          secretName: sealed-secrets-tls-secret

from sealed-secrets.

Recommend Projects