kai-scheduler/kai-scheduler Helm chart

What it is. kai-scheduler/kai-scheduler v0.16.9, as 37 Kubernetes objects in its default preset.

Install it. curl -fsSL -o try-objects.sh https://confighub.github.io/helm-expt/site/sh/kai-scheduler-kai-scheduler-v0-16-9/default/try-objects.sh && bash try-objects.sh

OCI bundle. oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/bundles/catalog-kai-scheduler-kai-scheduler-v0-16-9-default:latest@sha256:8063202c689d2cd7221cad04da18d409462c7d78049ee75472d88e9c5bd971c5

Needs first. Before an install or an upgrade, move the CRDs forward and migrate topologies. Helm runs these in hook-weight order before it applies the chart's objects. The listing gives the rest.

How it works. How the model works, and Helm in the Catalog.

Pick a version and a base

Versions are listed newest first. Each row is one base, and every cell is read from that base's listing. A base marked watch has a checked result with a limit to review.

v0.16.9 newest

2 bases. The installer package is published and signed. Open the page for v0.16.9.

Base	Objects	Flattening verdict	Published as OCI	Flag	Open
default default	37	flatten-with-routes, plan recorded	Published	watch	exact objects · listing
aicr-eks-training	37	flatten-with-routes, plan recorded	Published	watch	exact objects · listing

v0.14.1

2 bases. The installer package is published and signed. Open the page for v0.14.1.

Base	Objects	Flattening verdict	Published as OCI	Flag	Open
default default	37	flatten-with-routes, plan recorded	Published	watch	exact objects · listing
aicr-eks-training	37	flatten-with-routes, plan recorded	Published	watch	exact objects · listing

See what changes

Choose two versions or two bases, then press Compare. The page fetches the two retained files and checks each file's SHA-256 against the digest its listing records. It then computes the diff on demand, in your browser, with the code that cub config diff runs. Nothing is precomputed or stored.

Run the same diff yourself

These commands fetch the same two files and compare them on your machine, with no account. They follow the pair you choose above. cub plugin install confighub/cub-workshop@v0.6.61 adds cub config diff.

# fetch the first retained file
$ curl -fsSL -o kai-scheduler-kai-scheduler-v0-14-1-default.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/kai-scheduler/kai-scheduler/v0.14.1/revisions/default/r001/rendered/release-objects.yaml

# fetch the second retained file
$ curl -fsSL -o kai-scheduler-kai-scheduler-v0-16-9-default.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/kai-scheduler/kai-scheduler/v0.16.9/revisions/default/r001/rendered/release-objects.yaml

# check the bytes against the two listings
$ shasum -a 256 kai-scheduler-kai-scheduler-v0-14-1-default.yaml kai-scheduler-kai-scheduler-v0-16-9-default.yaml
a0cf177775ec0bf2532012da868de07c070a4fb6d6f792a9518089c5b0bc7b46  kai-scheduler-kai-scheduler-v0-14-1-default.yaml
7254c6c835430dbc6c8513ccb0d7d5a94b2d4fd0cdc7d4029fed5e13c541dd76  kai-scheduler-kai-scheduler-v0-16-9-default.yaml

# count what changes
$ cub config diff kai-scheduler-kai-scheduler-v0-14-1-default.yaml kai-scheduler-kai-scheduler-v0-16-9-default.yaml --summary

# list every changed field
$ cub config diff kai-scheduler-kai-scheduler-v0-14-1-default.yaml kai-scheduler-kai-scheduler-v0-16-9-default.yaml

Read one line for each version step

These lines are the only diff content this page stores. Each one was computed when the site was generated, by the same code, on the default base of both versions.

From v0.14.1 to v0.16.9 on the default base, 8 of 37 objects change, 2 are added and 2 are removed. Compute this diff.

Use this entry in ConfigHub

Every Catalog entry page carries these five steps in this order. Each step says what the Catalog has run for this entry, and a step with a missing precondition gives no command.

Steps 1 and 2 need no account. Install the cub CLI before any cub command. Step 2 uses cub config diff, which cub plugin install confighub/cub-workshop@v0.6.61 adds. A live walk on 2026-10-08 ran steps 3 to 5 for bitnami-nginx-24-0-2-http-clusterip and nvidia-gpu-operator-v26-3-3-default. These commands carry the changes that walk needed. It is a dated log and no receipt, so no state on this page rests on it. These are the steps for v0.16.9, the newest version, on its default base.

This entry is flagged for review. The kai-config object that tells the operator which scheduler services to run is delivered by a Helm hook, and no base holds it, so should it be part of the base instead of a lifecycle action that nothing runs automatically?

What is fixed, and what you supply

Fixed when this entry was built. These went into the build, so the objects already carry them. To change one, build the entry again from its source.

chart is kai-scheduler/kai-scheduler
version is v0.16.9
base is default
valuesProfile is recipes/kai-scheduler/kai-scheduler/v0.16.9/effective-values.yaml
namespace is kai-scheduler
releaseName is kai-scheduler
capabilityProfile is {"apiVersions":[],"kubeVersion":"1.31.0"}

Yours to supply or check. The destination must have these before the objects are applied. The words in italics say what the Catalog knows about each.

CRD included in this base; it must be established before Kubernetes accepts the rendered Queue and SchedulingShard objects and before the operator starts Declared. Not checked on any destination.
CRD included in this base; it must be established before Kubernetes accepts the rendered Queue and SchedulingShard objects and before the operator starts Declared. Not checked on any destination.
CRD included in this base; it must be established before Kubernetes accepts the rendered Queue and SchedulingShard objects and before the operator starts Declared. Not checked on any destination.
CRD included in this base; it must be established before Kubernetes accepts the rendered Queue and SchedulingShard objects and before the operator starts Declared. Not checked on any destination.
CRD included in this base; it must be established before Kubernetes accepts the rendered Queue and SchedulingShard objects and before the operator starts Declared. Not checked on any destination.
CRD included in this base; it must be established before Kubernetes accepts the rendered Queue and SchedulingShard objects and before the operator starts Declared. Not checked on any destination.

This entry's plan, and how to test it

These are the steps that plain objects cannot carry. ConfigHub stores them and does not carry them out. The words in italics say what the Catalog knows about each.

Before you deliver. Install and establish the 6 CRDs before the other objects. The base holds two Queue objects and a SchedulingShard, which Kubernetes rejects until their CRDs are established, and the operator watches all six kinds as soon as it starts. The listing gives the rest. Who: delivery workflow. Written down. Not run by the Catalog.
Around an install. Before an install or an upgrade, move the CRDs forward and migrate topologies. Helm runs these in hook-weight order before it applies the chart's objects. The listing gives the rest. Who: delivery workflow. Written down. Not run by the Catalog.
Around an install. After an install or an upgrade, apply the Config that tells the operator what to run. In this chart version the kai-config Config object is not a chart object. The listing gives the rest. Who: delivery workflow. Written down. Not run by the Catalog.
Around a delete. After a delete, remove what the operator created. The post-delete-cleanup Job deletes the Deployments the operator created in the release namespace and the kai-config Config object, with its own ServiceAccount, ClusterRole and ClusterRoleBinding. The listing gives the rest. Who: delivery workflow. Written down. Not run by the Catalog.
Once the destination is known. Helm was asked to keep these objects when the release goes away. A reconciler that prunes anything absent from its desired state will delete them instead, and for a custom resource definition that takes every resource of that kind with it. The listing gives the rest. Who: whatever applies the objects. Written down. Not run by the Catalog.

Test the install steps yourself. This script carries them out with kubectl on a cluster you choose, with no account. Read it first and use a throwaway cluster. The Catalog ran it on a local cluster, and the log has every line.

Test the plain objects. A second script tests the retained objects themselves with kubectl, and it needs no cub and no account. The Catalog has no recorded run of this script.

Read what a plan is, and why some entries have one.

1. Get the exact objects Run for this entry

The Catalog rendered this entry and retains its 37 objects in one file.

An upload can create more Units than the objects counted here. The installer renders a Namespace, and the upload adds an installer-record Unit.

Here is what the command does. cub installer is an open-source plugin for the cub CLI. cub installer setup pulls a catalog package and writes its Kubernetes files locally, leaving delivery to kubectl, Argo CD or Flux. The generated scripts stop before doing any work when the plugin or kustomize is missing.

# fetch the retained objects for this entry
$ curl -fsSL -o kai-scheduler-kai-scheduler-v0-16-9-default.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/kai-scheduler/kai-scheduler/v0.16.9/revisions/default/r001/rendered/release-objects.yaml

# check the bytes against the listing
$ shasum -a 256 kai-scheduler-kai-scheduler-v0-16-9-default.yaml
7254c6c835430dbc6c8513ccb0d7d5a94b2d4fd0cdc7d4029fed5e13c541dd76  kai-scheduler-kai-scheduler-v0-16-9-default.yaml

# render this base from the signed package; step 3 uploads this directory
$ cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/kai-scheduler-kai-scheduler:v0.16.9@sha256:7d360f97ada7c492e506acdd433c9212d21f5a6d26d8d8cbf1f0b68a268e94ab --base default --work-dir ./kai-scheduler-kai-scheduler-v0-16-9-default --non-interactive --namespace kai-scheduler

2. Compare with another version or base Not run for this entry

The listing records no comparison for this entry. The commands run on the retained files, with no account. This version has one other base in the Catalog, aicr-eks-training. The Catalog holds one other version, v0.14.1.

# fetch the aicr-eks-training base of the same version
$ curl -fsSL -o kai-scheduler-kai-scheduler-v0-16-9-aicr-eks-training.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/kai-scheduler/kai-scheduler/v0.16.9/revisions/aicr-eks-training/r001/rendered/release-objects.yaml

# list what differs between the two bases
$ cub config diff kai-scheduler-kai-scheduler-v0-16-9-default.yaml kai-scheduler-kai-scheduler-v0-16-9-aicr-eks-training.yaml --summary

# fetch the default base at version v0.14.1
$ curl -fsSL -o kai-scheduler-kai-scheduler-v0-14-1-default.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/kai-scheduler/kai-scheduler/v0.14.1/revisions/default/r001/rendered/release-objects.yaml

# list what changed from v0.14.1 to v0.16.9
$ cub config diff kai-scheduler-kai-scheduler-v0-14-1-default.yaml kai-scheduler-kai-scheduler-v0-16-9-default.yaml --summary

3. Upload it as a variant Not run for this entry

The Catalog has not uploaded this entry. The commands use its signed installer package. Read the log of the live walk on 2026-10-08.

Replace each value in angle brackets with a name of your own. The entry id may already exist as a Space in your organization, and the package name as a Component.

In the live walk, a Space named for the nginx entry's id and a Component named bitnami-nginx already existed, so the walk chose its own names. The --component flag sets the Component label the upload writes on the Space, which is the package name when you omit it.

The cub installer plugin reads your organization from CUB_CONTEXT and ignores --context. If you use a context other than your default, export CUB_CONTEXT first, or the plugin works in your default organization.

# sign in; steps 3 to 5 write to your ConfigHub organization
$ cub auth login

# upload step 1's directory as a Space of Units, under names you choose
$ cub installer upload --work-dir ./kai-scheduler-kai-scheduler-v0-16-9-default --space <your-space> --component <your-component>

# list the Units the upload created
$ cub unit list --space <your-space>

4. Deploy it Not run for this entry

No delivery run is recorded for this entry. Argo CD has not run, Flux has not run, and kubectl has not run. The commands name the Target workshop/target, which cub cluster up --name workshop creates on a local kind cluster with Argo CD. Use your own Target for a real destination. The base carries 6 CRDs it needs, so the destination does not supply them. Read the log of the live walk on 2026-10-08.

Use the Space name you chose in step 3. The delete command is needed because the cloned installer-record Unit carries the Target and Argo CD v3.5.4 cannot read it, a defect seen on cub v0.8.7 and server v0.8.9.

Without that line the walk deployed nothing and Argo CD showed Unknown, while every cub command exited 0. The walk ran the four commands in this order and did not try them without the first publish.

ConfigHub shows nothing when Argo CD fails to read a Release. Run kubectl -n argocd get applications.argoproj.io and read the Sync column, because Healthy alone is not a pass. Argo CD took between 18 seconds and about 5 minutes to read a Release on a cluster made without argobot.

The walk made its cluster with cub cluster up --no-argobot. That command creates two Spaces, a Worker, a Target and a Trigger, opens ports 30010 to 30019 on the machine, and installs Argo CD from an unpinned upstream manifest.

Removing the ConfigHub side does not remove the workload. In the walk, deleting the Application Unit and the Spaces left the Application and its pods running, because the root Application does not prune.

# clone the base onto a Target as a dev variant
$ cub variant create dev <your-space> --target workshop/target --space-pattern "template:<your-space>-dev"

# publish the Release that the cluster's Argo CD pulls
$ cub release publish <your-space>-dev

# delete the installer record, which Argo CD cannot read
$ cub unit delete --space <your-space>-dev installer-record

# publish again without it
$ cub release publish <your-space>-dev

5. Promote a change Not run for this entry

No promotion is recorded for this entry. Promotion carries a change in the base to the dev variant. The base changes when you edit a Unit or upload a newer version into the same Space. Read the log of the live walk on 2026-10-08.

The promotion changes the dev Space and publishes nothing. It also adds the installer-record Unit back with the Target. The change reaches the cluster only after the delete and the publish.

The preview lists the whole installer record as added. In the walk, the preview of a one-label change to gpu-operator ran to 405 lines, and about 400 of them were that record.

# preview what the dev variant would take from the base
$ cub variant promote <your-space>-dev --dry-run -o mutations

# promote once you have read the preview
$ cub variant promote <your-space>-dev --change-desc "Pull the reviewed base forward"

# delete the installer record that the promotion adds back
$ cub unit delete --space <your-space>-dev installer-record

# publish the Release that carries the change
$ cub release publish <your-space>-dev

For agentsThese steps are the nextSteps array of kai-scheduler-kai-scheduler-v0-16-9-default.json. Each state was read from flattened.retainedObjects, flattened.inventory, source.ociRef, oci.bundles, oci.runtimes, lifecycle.promotion, lifecycle.coverage and variants.known in the same listing. A command marked needsAccount there contacts ConfigHub. A step's notes hold its cautions, carries lists the CRDs the base brings, and liveWalk links the dated log that ran its commands.

Use another version or base

Every other base carries the same five steps, with its own states and commands, on the page of its version.

The same five steps on the page for v0.16.9 cover the base aicr-eks-training.
The same five steps on the page for v0.14.1 cover the bases default, aicr-eks-training.

Read this page as data

One file holds everything on this page in a form a program can read.

Technical notes and disclaimers

The plain-objects script stops before it applies anything. One step of the plan is yours to do first, and it prints it. When you run it again it applies the objects and ends. It does not wait for the workloads to start. Neither script runs the steps the plan names for an upgrade or a delete.