Chainguard Container for klipper-helm

Helm integration job image for K3s/RKE2 with automated chart lifecycle management

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/klipper-helm:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The Chainguard klipper-helm container image is a drop-in replacement for the upstream rancher/klipper-helm image. It provides the same functionality for managing Helm charts in K3s clusters, including support for essential Helm plugins like helm-mapkubeapis and helm-set-status. This image is designed to be a minimal, secure alternative that runs as a non-root user. Switching to this image should not require any changes to your existing deployment configuration.

Getting Started

The klipper-helm image provides Helm functionality for use within clusters. It supports operations such as installing, upgrading, and deleting Helm charts with built-in plugins like mapkubeapis and set-status.

First, create the ServiceAccount and RBAC configuration:

cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: ServiceAccount
metadata:
  name: klipper-helm-sa
  namespace: default
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: klipper-helm-admin
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
- kind: ServiceAccount
  name: klipper-helm-sa
  namespace: default
EOF

Then, deploy a Helm Release by running klipper-helm as a Pod

cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: Pod
metadata:
  name: helm-install-nginx
  namespace: default
spec:
  serviceAccountName: klipper-helm-sa
  restartPolicy: Never
  containers:
  - name: klipper-helm
    image: cgr.dev/ORGANIZATION/klipper-helm:latest
    command: ["entry"]
    args: ["install"]
    env:
    - name: NAME
      value: "test-nginx"
    - name: TARGET_NAMESPACE
      value: "default"
    - name: CHART
      value: "test-nginx/ingress-nginx"
    - name: REPO
      value: "https://kubernetes.github.io/ingress-nginx"
EOF

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard registry.

Documentation and Resources

• Klipper-helm Github Repository

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.