# The rtx-pro-6000-eks-ubuntu-training overlay, mirrored as a catalog entry

UNOFFICIAL/EXPERIMENTAL. This entry belongs to
[the AICR catalog overview](./index.md). It was produced by
`scripts/generate-aicr-from-overlay.mjs rtx-pro-6000-eks-ubuntu-training`, the generator built
to mirror any overlay from NVIDIA's AICR recipe catalog into a first-class
entry at the same bar as this catalog's other entries: source pinned by
digest, render checked, one digest over the whole rendered shape.

## What it is

Criteria `--service eks --accelerator rtx-pro-6000 --os ubuntu --intent training` resolves seven overlays into 14 components,
and the Argo CD bundle renders into 15 Applications (one platform root plus one
Application per rendered component, and some components render more than one
Application for their own pre- or post-install step).

```bash
aicr recipe --service eks --accelerator rtx-pro-6000 --os ubuntu --intent training --output recipe.yaml
aicr bundle --recipe recipe.yaml --deployer argocd-helm --output ./argocd-helm-bundle \
  --storage-class gp3 --accelerated-node-selector nvidia.com/gpu.present=true \
  --workload-selector app.kubernetes.io/part-of=training
helm template aicr-argocd ./argocd-helm-bundle --namespace argocd \
  --set repoURL=oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt --output-dir rendered
```

The [generation receipt](../../../examples/aicr/rtx-pro-6000-eks-ubuntu-training/generation-receipt.yaml)
records the exact commands, the criteria, and the release binary this entry
was built with: AICR v0.21.0, verified against the checksum published
in that release before it ran.

## One digest pins this entry too

```bash
node scripts/generate-aicr-digest-index.mjs --verify --example rtx-pro-6000-eks-ubuntu-training
```

The [digest index](../../../examples/aicr/rtx-pro-6000-eks-ubuntu-training/digest-index/README.md)
pins the upstream source, the recipe criteria, and all 15 Applications
under one platform digest. The compiler is a generic one shared by every
entry in this catalog, not something built new for this one.

## What is proven and what is not

Proven: the entry was generated by a binary verified against a checksum
pinned before it ran, the recipe and every rendered Application are retained
byte for byte, and one digest pins the shape.

Not proven, and stated rather than implied: this entry was never published,
so it carries no public digest and no OCI transport receipts, and the
repository reference in its Applications is what a publication would use
rather than a record that one happened. No ConfigHub import or promotion
exists for it, no cluster ever ran it, and no NGC surface was contacted.