kube-webhook-certgen-jkroepke
Kube-Webhook-Certgen-Jkroepke Overview
Secure your stack with a hardened Kube-Webhook-Certgen-Jkroepke 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.
Kube-Webhook-Certgen-Jkroepke is a community-maintained fork of the Kubernetes admission webhook certificate generator that adds support for patching multiple webhook configurations in a single invocation. It is commonly used with the ingress-nginx Helm chart to automate TLS certificate management for Kubernetes admission webhooks.
Try It Out
Prerequisites
- A running Kubernetes cluster (v1.21 or higher is recommended)
- Helm v3.8 or higher for OCI support (Installation instructions)
kubectlinstalled and configured
Step 1: Start Cluster
If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions
Step 2: Add Repository to Your Local Client
Add the official Helm chart repository to your local Helm client:
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo updateStep 3: Create a Local YAML File to Override Chart Defaults
Save the code below to a values.yaml file in your project directory to configure ingress-nginx to use the Minimus kube-webhook-certgen-jkroepke image:
cat <<EOF > values.yaml
controller:
admissionWebhooks:
patch:
image:
registry: reg.mini.dev
image: kube-webhook-certgen-jkroepke
tag: latest
digest: ""
EOFFor the purpose of this test, we pass the Minimus token inline. Standard practice is to create a Kubernetes secret. Learn more
Step 4: Deploy the Chart
Deploy the Helm chart using your values.yaml file:
helm upgrade --install ingress-nginx ingress-nginx/ingress-nginx -f values.yamlStep 5: Monitor Pod Status
Verify the deployment by checking that the admission webhook jobs complete successfully:
kubectl get pods -AYou should see something like:
ingress-nginx-admission-create-xxxx Completed
ingress-nginx-admission-patch-xxxx CompletedTechnical Considerations
The kube-webhook-certgen-jkroepke image provided by Minimus is a slim, security-hardened alternative to the public image from GitHub Container Registry. The images are largely interchangeable, with a few differences as noted below.
Kube-Webhook-Certgen-Jkroepke built by Minimus:
- Runs as non-root by default as user 1000. The public image runs as user [VERIFY: run
docker inspect ghcr.io/jkroepke/kube-webhook-certgen --format '{{.Config.User}}']. - 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.
- See the risk reduction dashboard for a detailed CVE comparison over the past 30 days.
- Review the compliance report to see the default hardening and security configurations for the image.
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.