1. Images & Charts
  2. cert-manager-webhook-pdns
cert-manager-webhook-pdns

cert-manager-webhook-pdns

Infra
Updated on July 27

PowerDNS cert-manager ACME webhook Overview

Secure your stack with a hardened PowerDNS cert-manager ACME webhook image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies contained in the image.


Use the PowerDNS cert-manager ACME webhook to let cert-manager complete ACME DNS01 challenges against a PowerDNS server. It creates and removes the TXT records needed to prove domain ownership, enabling automated issuance and renewal of certificates for zones hosted in PowerDNS.


Try It Out

Prerequisites

  • A running Kubernetes cluster with cert-manager installed
  • Helm
  • Access to a PowerDNS server with its API enabled

Step 1: Add Repository to your Local Client

Add the Helm chart to your local Helm client.

helm repo add cert-manager-webhook-pdns https://zachomedia.github.io/cert-manager-webhook-pdns
helm repo update

Step 2: Deploy via Helm Chart

helm install cert-manager-webhook-pdns cert-manager-webhook-pdns/cert-manager-webhook-pdns \
    --namespace cert-manager \
    --set image.repository=reg.mini.dev/cert-manager-webhook-pdns \
    --set image.tag=latest

Wait a minute and check that the Pods are up and running:

kubectl -n cert-manager get po

Confirm that Minimus images were deployed:

kubectl -n cert-manager describe pods | grep Image:

Step 3: Clean Up

Uninstall the chart to delete the resources it created, including Pods, Deployments, Services, Secrets, ConfigMaps, etc.:

helm uninstall cert-manager-webhook-pdns -n cert-manager

Technical Considerations

The PowerDNS cert-manager ACME webhook image provided by Minimus is a slim, security-hardened alternative to the public image.

PowerDNS cert-manager ACME webhook built by Minimus:

  1. Runs as root to support required functions in alignment with the public image.
  2. The Helm chart's default securityContext overrides this at deploy time, running the container as uid/gid 100 regardless of the image's own root default.
  3. The entrypoint is under /usr/bin/webhook. The public image entrypoint is under /usr/local/bin/webhook.
  4. Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.

The Payoff

A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.


Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.