Chainguard Container for rancher-fleet-fips

Deploy workloads from Git to large fleets of Kubernetes clusters

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/rancher-fleet-fips:latest

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

Compatibility Notes

rancher-fleet-fips is composed of multiple images:

• cgr.dev/ORGANIZATION/rancher-fleet-fips:latest
• cgr.dev/ORGANIZATION/rancher-fleet-agent-fips:latest

Chainguard's rancher-fleet-fips container images are comparable to the official rancher/fleet and rancher/fleet-agent images.

Getting Started

Installation with Helm Using values.yaml

There is an official documentation available in the Rancher Fleet website, you can find it here.

Create a values.yaml, specifying the Chainguard images:

cat <<EOF > values.yaml
image:
  repository: cgr.dev/ORGANIZATION/rancher-fleet-fips
  tag: latest

agentImage:
  repository: cgr.dev/ORGANIZATION/rancher-fleet-agent-fips
  tag: latest
EOF

Install the Helm chart for Rancher Fleet using the following command:

helm -n cattle-fleet-system install --create-namespace --wait fleet-crd fleet/fleet-crd
helm -n cattle-fleet-system install --create-namespace --wait fleet fleet/fleet  --values values.yaml

Following that, you can use kubectl to check whether the puds are running:

kubectl get pods -n cattle-fleet-system

NAME                               READY   STATUS    RESTARTS   AGE
fleet-agent-0                       2/2     Running   0          86s
fleet-controller-57689f8757-8d4cn   3/3     Running   0          102s
gitjob-59d66b6b8-jv2f8             1/1     Running   0          102s

You should now have Rancher Fleet with the Chainguard Rancher Fleet Agent running in your cluster.

Documentation and Resources

For more information on working with Rancher Fleet, please refer to the official documentation.

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

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.