This is one of the NVIDIA AICR pages. Start there if you are new to AICR.
1. Where the selected configuration came from
The provider chooses the recipe. ConfigHub Workshop records that choice before it keeps the generated objects as a base. Later ConfigHub variants are changes to that retained base; they do not rewrite the provider's catalog record.
| Record | Exact v0.20.0 value |
|---|---|
| Provider | NVIDIA · provider source |
| Provider catalog | NVIDIA AICR built-in catalog v0.20.0 · sha256:676f2d59eacd79ae1b72e5cbe00216b577def1da412dbdabb032f317a62dc1d8 |
| Selected recipe | h100-eks-ubuntu-training-kubeflow · accelerator=h100, intent=training, os=ubuntu, platform=kubeflow, service=eks |
| Retained base | 17 exact Argo CD Applications plus source and lifecycle records |
| ConfigHub handoff | The upload receipt carries the same provider, catalog digest, selected variant, and dimensions |
Open the complete source-catalog record · Open the retained BaseVariantRecord. Provider evidence applies to the selected recipe. ConfigHub evidence starts with the exact retained objects and records later changes, promotion, release, and delivery separately.
2. What the retained-configuration example proves
The public AICR configuration can be pulled without signing in. The seven selected Applications match their reviewed hashes, and the local OCI returns the same files.
The CPU starter is a ConfigHub Workshop selection from an AICR-generated platform. It is not an upstream NVIDIA AICR recipe. It keeps the source files unchanged, including a gp3 storage-class setting that must be changed before use on a cluster without that class.
An AI can propose that change, but a checker decides whether to accept it. The recorded example keeps all seven Application identities, changes only kube-prometheus-stack, and changes only its StorageClass field. A second request also moves a namespace, so the checker refuses it and writes no candidate.
Compare the accepted and refused requests.
Read the recorded anonymous run · Read how the selection was made · See the separate live CPU inference result
Open the AICR v0.20.0 starting configuration to inspect the most fully recorded recipe, 17 exact Applications, all 16 nested source renders, and the separate Argo CD and Flux lifecycle plans. The records bind 409 local objects to exact chart, values, and output digests without claiming that a GPU target ran. Read the nested and destination result. The v0.19.0 entry continues further into ConfigHub variants and release OCI.