1. Images & Charts
  2. trust-manager
trust-manager

trust-manager

Infra
Updated 4 days ago

Trust-Manager Overview

Secure your stack with a hardened Trust-Manager 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.


Trust Manager is an operator for distributing trust bundles in Kubernetes clusters. Trust Manager is part of the cert-manager toolkit for provisioning and managing TLS certificates in Kubernetes.


Try It Out

We will deploy Trust Manager using a Helm chart.

Prerequisites

  • A running Kubernetes cluster (v1.21 or higher is recommended)
  • Helm v3.8 or higher for OCI support (Installation instructions)
  • kubectl installed 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 jetstack https://charts.jetstack.io
helm repo update

Step 3: Create a Local YAML File to Override Chart Defaults

Save the code below to a values.yaml file in your project directory:

# Image configuration for Minimus registry
image:
  repository: reg.mini.dev/trust-manager
  tag: latest

# Webhook configuration
app:
  webhook:
    tls:
      helmCert:
        enabled: true

Note the recommended pull policy for Minimus images.

Step 4: Deploy Trust-Manager

Trust-Manager is usually deployed along with cert-manager, so it requires both the cert-manager and trust-system namespaces.

Deploy the chart from the same project directory where the values.yaml file is located:

helm upgrade --install trust-manager jetstack/trust-manager \
  --namespace trust-system \
  --create-namespace \
  -f values.yaml

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

kubectl -n trust-system get po

Step 5: Check the log file

View the trust-manager logs (Update the command with your exact Pod name) to verify that the webhook is available:

kubectl -n trust-system logs -f trust-manager-{POD-ID} | grep webhook

You should see the following logs:

time=2025-09-04T12:54:47.237Z level=INFO msg="Starting webhook server" logger=controller-runtime/webhook
time=2025-09-04T12:54:47.237Z level=INFO msg="Serving webhook server" logger=controller-runtime/webhook host=0.0.0.0 port=6443

Technical Considerations

The Trust-Manager image provided by Minimus is a slim, security-hardened alternative to the public image from Docker Hub. The images are largely interchangeable, with a few differences as noted below.

Trust-Manager built by Minimus:

  1. Runs as non-root by default for a security-first approach that protects against privilege escalation attacks. The public image runs as root.
  2. 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.