minimus-k8s

Migrates Kubernetes manifests, Helm charts, and Kustomize overlays to Minimus distroless images.

20|Updated Jul 23, 2026
One-click install
npx skills add https://github.com/minimusio/ai-integration --skill minimus-k8s-minimusio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: minimus-k8s
Source: https://github.com/minimusio/ai-integration/tree/main/plugins/cursor/skills/minimus-k8s
Command: npx skills add https://github.com/minimusio/ai-integration --skill minimus-k8s-minimusio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Kubernetes workloads running on public Docker Hub images carry large CVE counts and often fail restricted security policies. This Skill guides AI agents through migrating raw manifests, Helm charts, and Kustomize overlays onto hardened Minimus distroless images from reg.mini.dev, handling the port, securityContext, probe, and shell-compatibility changes that a naive image swap breaks. ## Core Features & Use Cases - Full image inventory and resolution: Enumerates every container, initContainer, and subchart image, then resolves each to its Minimus equivalent via the public images.minimus.io gallery with correct version-line and tag selection. - Pod spec adaptation: Aligns securityContext with the image's User, rewrites ports (e.g. nginx 80 to 8080), replaces shell-based probes and command wrappers with direct exec or httpGet, and configures the minimus-registry pull secret. - Asset-type-aware migration and verification: Applies minimal diffs for raw manifests, values-only overrides for third-party Helm charts (including Bitnami's allowInsecureImages gate), the images transformer for Kustomize, then verifies with helm template, kustomize build, throwaway kind/minikube dry-runs, and docker manifest inspect. - Use Case: Ask the agent to migrate a Helm release off bitnami/nginx — it overrides image registry/repository/tag in values, updates the Service targetPort to 8080, swaps the exec probe for httpGet, adds the pull secret, and renders the chart to prove every image reference points at reg.mini.dev. ## Quick Start Migrate my Kubernetes deployment manifests to use Minimus hardened images and verify the result.

Frequently Asked Questions about minimus-k8s

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Kubernetes manifests to distroless images?

Inventory every image reference including initContainers and sidecars, resolve each to a Minimus equivalent at images.minimus.io, then adapt securityContext, ports, probes, and command overrides to the image's spec. Finish by rendering, dry-run validating on a throwaway kind or minikube cluster, and confirming each tag exists with docker manifest inspect.

How do I override images in a third-party Helm chart?

Use values overrides only, never edit vendored templates. Find image knobs with helm show values, override every rendered image including subcharts, and for Bitnami charts set image.registry, image.repository, image.tag plus global.security.allowInsecureImages=true.

Why does my pod CrashLoopBackOff after switching to a distroless image?

Distroless images have no shell or coreutils, so exec probes, lifecycle hooks, or command wrappers using /bin/sh fail. Rewrite them as httpGet or tcpSocket probes, direct-exec command/args, or move shell work to a busybox initContainer.

Does Minimus nginx listen on port 80?

No. Minimus images run non-root, so nginx listens on 8080 instead of 80. Update containerPort, Service targetPort, probes, and NetworkPolicies to the port from the image's specification page while keeping the Service's external port unchanged.

Do I need a pull secret for reg.mini.dev images?

Yes. Cluster nodes authenticate with a Minimus registry token via a docker-registry secret named minimus-registry, referenced in each pod spec's imagePullSecrets or attached to the workload's ServiceAccount. The secret must exist in every namespace that pulls the images.

When should I not use a Minimus -dev image tag?

Never deploy -dev tags to a cluster. The -dev variant adds a shell and apk for image build stages only; production workloads must use the pinned production line tag such as 1.31 or 22.