Chainguard Container for rke2-cloud-provider-fips

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/rke2-cloud-provider-fips:latest

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

Using the Chainguard RKE2 Cloud Provider

Replacing the Default Cloud Provider

To use the Chainguard RKE2 cloud provider image instead of the default implementation, configure your RKE2 cluster to use the hardened image:

# /etc/rancher/rke2/config.yaml
cloud-provider-name: external
kube-apiserver-arg:
  - cloud-provider=external
kube-controller-manager-arg:
  - cloud-provider=external
kubelet-arg:
  - cloud-provider=external

Then deploy the Chainguard cloud provider as a DaemonSet or deployment in your cluster:

apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: rke2-cloud-provider
  namespace: kube-system
spec:
  selector:
    matchLabels:
      app: rke2-cloud-provider
  template:
    metadata:
      labels:
        app: rke2-cloud-provider
    spec:
      containers:
      - name: rke2-cloud-provider
        image: cgr.dev/ORGANIZATION/rke2-cloud-provider-fips:latest
        # Add necessary configuration and arguments

Documentation and Resources

• RKE2 Cloud Provider Configuration
• Rancher Cloud Provider Setup
• Upstream 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.