Chainguard Container for vc-scheduler-fips

A Kubernetes-native batch scheduling system, extending and enhancing the capabilities of the standard kube-scheduler.

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/vc-scheduler-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

volcano-fips is comprised of 3 images:

cgr.dev/ORGANIZATION/vc-scheduler-fips cgr.dev/ORGANIZATION/vc-controller-manager-fips cgr.dev/ORGANIZATION/vc-webhook-manager-fips

The Chainguard images run as 'non root', whereas the upstream images default to running as 'root'. Only the minimum set of tools and dependencies are installed.

FIPS Support

The volcano-fips Chainguard Image Group ships with a validated redistribution of the OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Images, consult the guide on FIPS-enabled Chainguard Images on Chainguard Academy.

Getting Started

We can use the volcano helm chart for testing the volcano images. We can create a values.yaml that'll override upstream images with Chainguard images.

image_registry               : cgr.dev
controller_image_name        : ORGANIZATION/vc-controller-manager-fips
scheduler_image_name         : ORGANIZATION/vc-scheduler-fips
admission_image_name         : ORGANIZATION/vc-webhook-manager-fips

Deploy volcano:

helm repo add volcano-sh https://volcano-sh.github.io/helm-charts
helm install volcano volcano-sh/volcano -n volcano-system --create-namespace -f values.yaml

Once deployed, validate the installation by creating a queue:

cat <<EOF | kubectl apply -f -
apiVersion: scheduling.volcano.sh/v1beta1
kind: Queue
metadata:
  name: test-queue
spec:
  weight: 1
  capability:
    cpu: "2"
    memory: "2Gi"
EOF

Create a job leveraging the queue:

cat <<EOF | kubectl apply -f -
apiVersion: batch.volcano.sh/v1alpha1
kind: Job
metadata:
  name: test-vcjob
  namespace: volcano-system
spec:
  minAvailable: 1
  schedulerName: volcano
  queue: test-queue
  maxRetry: 3
  policies:
    - event: PodEvicted
      action: RestartJob
  tasks:
    - replicas: 1
      name: worker
      template:
        spec:
          restartPolicy: OnFailure
          containers:
            - name: test-container
              # This example uses the Chainguard busybox image for demonstration purposes.
              image: cgr.dev/chainguard/ORGANIZATION/busybox-fips:latest
              command: ["sh", "-c", "echo 'Hello from Volcano' && sleep 10"]
              resources:
                requests:
                  cpu: "100m"
                  memory: "128Mi"
EOF

Documentation and Resources

• Official Documentation
• Getting Started

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.