What it is. kai-scheduler/kai-scheduler v0.14.1, as 37 Kubernetes objects in its default preset. The Catalog holds 2 presets of this version.
Install it. curl -fsSL -o try-objects.sh https://confighub.github.io/helm-expt/site/sh/kai-scheduler-kai-scheduler-v0-14-1/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-14-1-default:latest@sha256:f891d16770a42343d82ccfe06b51030e04987468b6c0349fa33750f21c4d5830
Needs first. Before an install or an upgrade, move the CRDs forward, migrate topologies and apply the Config. 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.
What this page gives you
This is a human-readable detail page for one retained package version. It keeps the package, base names, exact OCI identity, and publication receipt reachable without pretending this retained-only version has the richer readiness evidence attached to the bold version in the component row.
Where its settings and observations live
Each packaged configuration records Helm-derived files and installer metadata. Later ConfigHub changes belong in governed variants. Target prerequisites and live observations remain separate facts; this publication receipt does not turn them into passes.
Four Separate Questions
Inspecting a source, producing objects, checking a destination, and checking a live result are different jobs. A Catalog match is useful for comparison but is not required. A missing destination or deployment is shown as not run or blocked, not as a failed configuration.
| Question | Current answer | What it needs | Status |
|---|---|---|---|
| What do I have? | Inspect the helm source, choices, locks, and any existing output before selecting a destination. | Destination access: no Selected configuration deployed: no | Available to inspect evidence recorded |
| What will it produce? | 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? | Destination access: no Selected configuration deployed: no | Checked: review the limit evidence recorded |
| Can this destination accept it? | The destination has not been checked for this exact configuration. A recorded source or render result is not a destination pass. | Destination access: yes Selected configuration deployed: no | Not run no run recorded |
| Did it work? | No post-deployment result is recorded for this exact configuration. Publication, upload, or rendering is not proof that it ran correctly. | Destination access: yes Selected configuration deployed: yes | Not run no run recorded |
Open the complete assessment, source, lifecycle, and evidence record.
Try This Chart
Inspect the exact package first, then choose one of the packaged configurations. The version remains readable in the reference, and the manifest digest prevents the registry from returning different package bytes. The setup command renders files locally; it does not apply them to Kubernetes.
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.
cub installer inspect oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/kai-scheduler-kai-scheduler:v0.14.1@sha256:5e7b31be9fa573c1d9eba1e990ac6ff678388be26754ab55b0fe0d4593f37510 --json
cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/kai-scheduler-kai-scheduler:v0.14.1@sha256:5e7b31be9fa573c1d9eba1e990ac6ff678388be26754ab55b0fe0d4593f37510 --base default --work-dir ./kai-scheduler-kai-scheduler-v0-14-1-default --non-interactiveRun shared local configuration checks after the package has written its Kubernetes YAML:
cub plugin install confighub/homebrew-tap@cub-scan-v0.7.3 --name scan
cub check --format json --output cub-check.json <work-dir>/out/manifestsThe check is advisory and does not apply anything.
Version tag: oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/kai-scheduler-kai-scheduler:v0.14.1
Exact package: oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/kai-scheduler-kai-scheduler:v0.14.1@sha256:5e7b31be9fa573c1d9eba1e990ac6ff678388be26754ab55b0fe0d4593f37510
The manifest digest comes from the committed publication receipt. cub installer refuses the pull if that exact manifest is not available.
Verify the package publisher
Run this command with cosign. It checks the expected publisher, the exact manifest digest, and the package annotations.
cosign verify --certificate-identity helm-expt-package-signer@nth-fort-499605-q5.iam.gserviceaccount.com --certificate-oidc-issuer https://accounts.google.com --annotations confighub.com/package-path=packages/kai-scheduler/kai-scheduler/v0.14.1 --annotations confighub.com/package-sha256=b1c28a877952e907a8100b1bbbac0472faae9410da17660bad1d9939149bf268 europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/kai-scheduler-kai-scheduler:v0.14.1@sha256:5e7b31be9fa573c1d9eba1e990ac6ff678388be26754ab55b0fe0d4593f37510A valid signature identifies who signed these package bytes. It does not show that the configuration is suitable for your cluster; use this page's checks and setup instructions for that decision.
Signature receipt · Sigstore bundle · How signature verification works
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. This page covers 2 entries, so open the one you want. 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.
Helm chart, base default, version v0.14.1
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.
chartiskai-scheduler/kai-schedulerversionisv0.14.1baseisdefaultvaluesProfileisrecipes/kai-scheduler/kai-scheduler/v0.14.1/effective-values.yamlnamespaceiskai-schedulerreleaseNameiskai-schedulercapabilityProfileis{"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, migrate topologies and apply the Config. 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 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 plain objects yourself. This script tests the retained objects themselves with kubectl, and it needs no cub and no account. Read it first and use a throwaway cluster. The Catalog has no recorded run of this script.
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.
# fetch the retained objects for this entry
$ 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
# check the bytes against the listing
$ shasum -a 256 kai-scheduler-kai-scheduler-v0-14-1-default.yaml
a0cf177775ec0bf2532012da868de07c070a4fb6d6f792a9518089c5b0bc7b46 kai-scheduler-kai-scheduler-v0-14-1-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.14.1@sha256:5e7b31be9fa573c1d9eba1e990ac6ff678388be26754ab55b0fe0d4593f37510 --base default --work-dir ./kai-scheduler-kai-scheduler-v0-14-1-default --non-interactive --namespace kai-scheduler2. 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.16.9.
# fetch the aicr-eks-training base of the same version
$ curl -fsSL -o kai-scheduler-kai-scheduler-v0-14-1-aicr-eks-training.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/kai-scheduler/kai-scheduler/v0.14.1/revisions/aicr-eks-training/r001/rendered/release-objects.yaml
# list what differs between the two bases
$ cub config diff kai-scheduler-kai-scheduler-v0-14-1-default.yaml kai-scheduler-kai-scheduler-v0-14-1-aicr-eks-training.yaml --summary
# fetch the default base at version v0.16.9
$ 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
# list what changes 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 --summary3. 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-14-1-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>-dev5. 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>-devHelm chart, base aicr-eks-training, version v0.14.1
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.
chartiskai-scheduler/kai-schedulerversionisv0.14.1baseisaicr-eks-trainingvaluesProfileisrecipes/kai-scheduler/kai-scheduler/v0.14.1/effective-values-aicr-eks-training.yamlnamespaceiskai-schedulerreleaseNameiskai-schedulercapabilityProfileis{"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, migrate topologies and apply the Config. 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.
- 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 plain objects yourself. This script tests the retained objects themselves with kubectl, and it needs no cub and no account. Read it first and use a throwaway cluster. The Catalog has no recorded run of this script.
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.
# fetch the retained objects for this entry
$ curl -fsSL -o kai-scheduler-kai-scheduler-v0-14-1-aicr-eks-training.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/kai-scheduler/kai-scheduler/v0.14.1/revisions/aicr-eks-training/r001/rendered/release-objects.yaml
# check the bytes against the listing
$ shasum -a 256 kai-scheduler-kai-scheduler-v0-14-1-aicr-eks-training.yaml
f5b5383ffa1072925cd6d639d4aa69cbdefa1b34ba4eaf75b33a698fd210a9c5 kai-scheduler-kai-scheduler-v0-14-1-aicr-eks-training.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.14.1@sha256:5e7b31be9fa573c1d9eba1e990ac6ff678388be26754ab55b0fe0d4593f37510 --base aicr-eks-training --work-dir ./kai-scheduler-kai-scheduler-v0-14-1-aicr-eks-training --non-interactive --namespace kai-scheduler2. 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, default. The Catalog holds one other version, v0.16.9.
# fetch the default base of the same version
$ 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 differs between the two bases
$ cub config diff kai-scheduler-kai-scheduler-v0-14-1-aicr-eks-training.yaml kai-scheduler-kai-scheduler-v0-14-1-default.yaml --summary
# fetch the aicr-eks-training base at version v0.16.9
$ 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 changes from v0.14.1 to v0.16.9
$ cub config diff kai-scheduler-kai-scheduler-v0-14-1-aicr-eks-training.yaml kai-scheduler-kai-scheduler-v0-16-9-aicr-eks-training.yaml --summary3. 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-14-1-aicr-eks-training --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>-dev5. 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>-devAvailable Configurations
default- package defaultaicr-eks-training
The section below says what these configurations expect you to provide.
Local Configuration Checks
We ran cub check v0.7.3 against the exact rendered objects for every configuration below. The result is advisory: read each finding and decide whether it matters for your target.
Scanner and ruleset identity
Pattern bundle: v0.7.3
Bundle manifest: sha256:0405f6ffe21e567adf5d6a732d181c7f228194920456d046b4338baeb14de1a8
Risk catalog: sha256:7ff79a126ad99bba2505fec8b2b7711c03f50eb362141128ec1c83e27a5036ba
| Configuration | Advisory result | Exact input | Checked | Evidence |
|---|---|---|---|---|
aicr-eks-training | 19 advisory findings 3 critical, 15 warning, 1 info Container does not set runAsNonRoot Container does not disable allowPrivilegeEscalation ClusterRole grants secrets read permissions | 37 objectssha256:0c958734fd09025ebc416f28c64425ab9448c643878233ced201881eaa521659 | 2026-10-08 | Full cub check resultExact YAML Separate Catalog review |
default | 19 advisory findings 3 critical, 15 warning, 1 info Container does not set runAsNonRoot Container does not disable allowPrivilegeEscalation ClusterRole grants secrets read permissions | 37 objectssha256:fb2317196c988a6dce0b443274766df096ba3929dd50175f2f74c320019e568a | 2026-10-08 | Full cub check resultExact YAML Separate Catalog review |
What this does not check: hook execution, CRD readiness, target Secrets and cloud services, admission behavior, workload health, or rollback. The linked Catalog review covers chart-specific source and operating questions. ConfigHub validation and approval are separate managed controls.
Read all shared check results and the mapping to Catalog rules.
What This Chart Contains
Shipping a chart as plain rendered YAML is faster and simpler, and it silently drops anything Helm was going to do afterwards. This section reports what a scan of the packaged chart found, across 51 files.
| Construct | Found | Why it matters when a chart ships as plain YAML |
|---|---|---|
| Helm hooks | 17 | Hook Jobs never fire, or fire under a different hook dialect. |
| Keep policy | 4 | A reconciler prunes what Helm promised to keep. |
| Cluster lookups | 9 | The chart reads the cluster while rendering, so a render without one is valid but wrong. |
| Custom resource definitions | 6 | Per-file delivery can race the definitions the resources depend on. |
A flattening-safety verdict has decided this version: aicr-eks-training:flatten-with-routes; default:flatten-with-routes. The verdict records one disposition per construct and names any companion artifact a flattened bundle must ship. What the flattening verdict means.
A construct being present does not make a chart unflattenable. Most are switched on or off by values, and a verdict records which ones the base you choose actually reaches. Read the catalog-wide evidence for how common each one is.
Images This Chart Pulls
Every reference below is read from the committed package bases, so what you see is what the packaged manifests name.
| Packaged base | Image references |
|---|---|
| default | description: Image is the configuration of the service imagedescription: Image is the image used by the resource reservationghcr.io/kai-scheduler/kai-scheduler/operator:v0.14.1 |
| aicr-eks-training | description: Image is the configuration of the service imagedescription: Image is the image used by the resource reservationghcr.io/kai-scheduler/kai-scheduler/operator:v0.14.1 |
What Has Been Tested
Choose the question you care about. Not checked means this catalog has no version-specific result; it is not a pass.
| Question | Status | Evidence |
|---|---|---|
| Can I pull these exact package bytes again? | Checked | Package receipt |
| What does this chart contain? | Not checked | No linked result |
| Does the recorded render match Helm? | Not checked | No linked result |
| Did the supplied values change the render? | Not checked | No linked result |
| Were hooks, CRDs, or setup steps checked? | Not checked | No linked result |
| Did this version run on a local Kubernetes cluster? | Not checked | No linked result |
| Did an OCI delivery through GitOps run? | Not checked | No linked result |
| Did Helm and ConfigHub reach the same live result? | Not checked | No linked result |
| Was the result compared on separate clusters? | Not checked | No linked result |
| Was a ConfigHub promotion tested? | Not checked | No linked result |
| Did this version string point at changed upstream bytes? | Not checked | No linked result |
The committed publication receipt binds this package path and OCI ref to layer sha256:b1c28a877952e907a8100b1bbbac0472faae9410da17660bad1d9939149bf268 and manifest sha256:5e7b31be9fa573c1d9eba1e990ac6ff678388be26754ab55b0fe0d4593f37510, and records an inspect-result digest.
You can check a pull yourself: the inspect command under Try This Chart prints the package's manifest and layer digests, and they must equal the receipted values above. If they differ, do not use the pulled package.
No version-specific runtime result is claimed here. The component row's readiness, caveats, and live evidence describe only its bold version. For that separate evidence, open the v0.16.9 evidence page.
What You Must Provide
The installer metadata records 12 external-requirement references across these configurations. Inspect the package before choosing a base.
Choose a namespace and target deliberately, supply any listed Secret, CRD, storage, API, or cloud prerequisite, and inspect the rendered YAML before delivery.
Before Production
Run target-specific policy, lifecycle, upgrade, and workload checks. A successful package publication and inspect result does not establish production support or live convergence.
Source And Evidence Files
| Record | Open |
|---|---|
| Retained package source | packages/kai-scheduler/kai-scheduler/v0.14.1 |
| Machine-readable listing (default) | site/listings/kai-scheduler-kai-scheduler-v0-14-1-default.json |
| Machine-readable listing (aicr-eks-training) | site/listings/kai-scheduler-kai-scheduler-v0-14-1-aicr-eks-training.json |
| Installer metadata | packages/kai-scheduler/kai-scheduler/v0.14.1/installer.yaml |
| Publication receipt | runs/installer-oci/kai-scheduler-kai-scheduler/v0.14.1/installer-package-publication-receipt.yaml |
| Publisher signature | runs/installer-oci-signatures/kai-scheduler-kai-scheduler/v0.14.1/signature-receipt.yaml |
| Sigstore bundle | runs/installer-oci-signatures/kai-scheduler-kai-scheduler/v0.14.1/signature.sigstore.json |
| Version tag | oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/kai-scheduler-kai-scheduler:v0.14.1 |
| Exact OCI ref | oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/kai-scheduler-kai-scheduler:v0.14.1@sha256:5e7b31be9fa573c1d9eba1e990ac6ff678388be26754ab55b0fe0d4593f37510 |
| Layer digest | sha256:b1c28a877952e907a8100b1bbbac0472faae9410da17660bad1d9939149bf268 |
| Manifest digest | sha256:5e7b31be9fa573c1d9eba1e990ac6ff678388be26754ab55b0fe0d4593f37510 |
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. The script does not run the steps the plan names for an upgrade or a delete.