kube-startup-cpu-boost

packaged by Chainguard

Chainguard Container for kube-startup-cpu-boost

Kube Startup CPU Boost is a controller that increases CPU resource requests and limits during Kubernetes workload startup time

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/kube-startup-cpu-boost:latest

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

Compatibility Notes

This image is built from source with Go and tracks upstream Kube Startup CPU Boost releases, licensed under the Apache License 2.0. It keeps the launch configuration of ghcr.io/google/kube-startup-cpu-boost:

• The entrypoint is /manager, matching the upstream image. The manager binary is installed at /usr/bin/kube-startup-cpu-boost, and /manager is a symlink to it.
• The image runs as the nonroot user (UID 65532) by default, like the upstream image.
• The image includes CA certificates for TLS connections to the Kubernetes API server.

Getting Started

Kube Startup CPU Boost is a Kubernetes operator. It ships a StartupCPUBoost custom resource and a mutating admission webhook that temporarily increases the CPU requests and limits of selected pods during startup, then reverts them once the startup window ends.

The recommended way to deploy it is the upstream Helm chart, overriding the image:

helm repo add kube-startup-cpu-boost https://google.github.io/kube-startup-cpu-boost
helm install kube-startup-cpu-boost kube-startup-cpu-boost/kube-startup-cpu-boost \
  --namespace kube-startup-cpu-boost-system --create-namespace \
  --set controllerManager.manager.image.repository=cgr.dev/ORGANIZATION/kube-startup-cpu-boost \
  --set controllerManager.manager.image.tag=latest

Once the controller is running, create a StartupCPUBoost resource that selects the pods to boost:

apiVersion: autoscaling.x-k8s.io/v1alpha1
kind: StartupCPUBoost
metadata:
  name: boost-demo
  namespace: default
selector:
  matchExpressions:
    - key: app
      operator: In
      values: ["boost-me"]
spec:
  resourcePolicy:
    containerPolicies:
      - containerName: app
        percentageIncrease:
          value: 50
  durationPolicy:
    podCondition:
      type: Ready
      status: "True"

Configuration

The controller listens on the following ports:

• 9443/TCP for the mutating admission webhook (TLS)
• 8080/TCP for Prometheus metrics
• 8081/TCP for the health and readiness probes

Refer to the upstream documentation for the full list of configuration options.

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.