Skip to content

Howto use wildcard certs in all namespaces with auto renewal ? #37

Description

@barnybadzoo

With Certs i can use acme.sh for a lot of dns providers which are not being coverd with cert-manager, what is really great.
I did specify the env value for my provider in values.yaml, and was able to get for a single host an valid cert with an ingress like you describe at your site.

I would like to know how can i setup a wildcard domain cert for use in all namespaces ?

What i would like to achieve is this:

  • Get a wildcard cert like this:
    acme.sh --issue --dns dns_doapi -d kube.example.com -d *.kube.example.com -d *.gitlab.kube.example.com -d *.ws.gitpod.kube.example.com -d *.pipe.kube.example.com
  • Import this cert as tls wildcard-domain-tls (can be done with kubectl)
  • Distribute it to all namespaces as wildcard-domain-tls
  • with a renewal Job which renews the cert and updates the tls in every namespace

Or is this all already done by cert ?

UPDATE: I did generate a wildcard certifcate through configuring an ingress with multiple hosts, and it is updated in the namespace i created it.. So the only thing left is to copy the secret across all namespaces.

copy from one to other namespace:
kubectl get secrets wildcard-domain-tls --namespace=<old-namespace> -o yaml | sed 's/namespace: <old-namespace>/namespace: <new-namespace>/' | kubectl apply -f -

Still need a job for this on reneal or change you crontab job..

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions