Skip to content

Latest commit

 

History

History
138 lines (114 loc) · 3.66 KB

README.md

File metadata and controls

138 lines (114 loc) · 3.66 KB
Raw

cert-manager-webhook-rackspace

A cert-manager webhook based dns01 solver supporting Rackspace Cloud DNS.

Installation

cert-manager

This package is an addon to cert-manager so to get started you must first have installed it. Instructions can be found here for installing it.

webhook

The webhook must be installed in the same namespace that you've installed cert-manager. This next step assumes it was cert-manager.

helm install --namespace cert-manager cert-manager-webhook-rackspace charts/cert-manager-webhook-rackspace

To uninstall you can run the following:

helm uninstall --namespace cert-manager cert-manager-webhook-rackspace

Usage with ClusterIssuer

To use the Rackspace Cloud DNS webhook, you must have an account with admin permissions to the Cloud DNS service and must know the Rackspace API key for that account.

An example secret to provide the credentials would be:

apiVersion: v1
kind: Secret
metadata:
  name: cert-manager-webhook-rackspace-creds
  namespace: cert-manager
type: Opaque
stringData:
  username: my-username-here
  api-key: my-api-key-here

Then you can create a ClusterIssuer. An example would be:

apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  name: letsencrypt-staging
spec:
  acme:
    # The ACME server URL
    server: https://acme-staging-v02.api.letsencrypt.org/directory

    # Email address used for ACME registration
    email: mail@example.com # REPLACE THIS WITH YOUR EMAIL!!!

    # Name of a secret used to store the ACME account private key
    privateKeySecretRef:
      name: letsencrypt-staging

    solvers:
    - dns01:
        webhook:
          groupName: acme.mycompany.com  # replace with the groupName you set for the helm chart
          solverName: rackspace
          config:
            # for a ClusterIssuer this secret will live in the cert-manager namespace
            # and will need to be named the deployment name + "-creds"
            authSecretRef: cert-manager-webhook-rackspace-creds
            domainName: some.domain.tld

You can then create a certificate like:

apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: example-cert
spec:
  commonName: something.some.domain.tld
  dnsNames:
    - something.some.domain.tld
  issuerRef:
    name: letsencrypt-staging
    kind: ClusterIssuer
  secretName: example-cert

Usage with Issuer

Using an Issuer is a bit more complicated since you must create the credentials secret in the namespace where your Issuer will live and give the cert-manager-webhook-rackspace ServiceAccount access to read it. In the example below it's assumed you'll be creating your secret named name-of-secret. Once this is done the steps will remain similar to the ClusterIssuer above.

apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: cert-manager-webhook-rackspace:secret-reader
rules:
  - apiGroups:
      - ""
    resources:
      - "secrets"
    resourceNames:
      - "name-of-secret"
    verbs:
      - "get"
      - "watch"
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: cert-manager-webhook-rackspace:secret-reader
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: cert-manager-webhook-rackspace:secret-reader
subjects:
  - apiGroup: ""
    kind: ServiceAccount
    name: cert-manager-webhook-rackspace
    namespace: cert-manager