1. Images & Charts
  2. metacontroller
metacontroller

metacontroller

Infra
Updated on July 27

Metacontroller Overview

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


Metacontroller is an add-on for Kubernetes that allows users to write and deploy custom controllers in the form of simple scripts by exposing a webhook-based API. Instead of writing full controller logic in Go, implement simple HTTP callbacks in any language and Metacontroller will handle the reconciliation loop, watch setup, and Kubernetes API interactions for you.


Try It Out

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: Deploy via Helm Chart

Update the chart version as appropriate and deploy:

helm install metacontroller oci://ghcr.io/metacontroller/metacontroller-helm \
  --version v4.10.3 \
  --namespace metacontroller \
  --create-namespace \
  --set image.repository=reg.mini.dev/metacontroller \
  --set image.tag=latest

Wait a minute and check that the Pod is up and running:

kubectl -n metacontroller get pods

Confirm that a Minimus image was deployed:

kubectl -n metacontroller describe pods | grep Image:

Step 3: Clean Up

Uninstall the chart to delete the namespace and its resources, including Pods, Deployments, Services, Secrets, ConfigMaps, etc.:

helm uninstall metacontroller -n metacontroller

Technical Considerations

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

Metacontroller built by Minimus:

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