AIM model catalog management

AIM model catalog management#

Entry point for cluster operators and platform administrators who manage the AIM model catalog on AMD Enterprise AI reference stack clusters. End users browse and deploy models from the catalog in AMD AI Workbench.

Detailed lifecycle rules, version policy, and step-by-step Gitea and Argo CD procedures live in the Cluster Forge repository (not duplicated here).

Operator guides (Cluster Forge)#

Topic	Guide
Catalog layers, version policy, filter vs source removal, responsibilities	AIM model catalog lifecycle
Add, replace, or remove entries; active hardware families; troubleshooting	Adding AIM catalog models

To list active hardware families on a cluster, use the fenced kubectl command in Before you start in Adding AIM catalog models (not duplicated here).

Portal configuration#

Topic	Guide
Set `AIM_HARDWARE_FAMILY` / `hardwareFamilies` at install	Installation configuration values
Upgrade the reference stack; dedupe before catalog or platform upgrade	Upgrade an existing installation

At a glance#

Enterprise AI reference stack clusters combine a packaged baseline catalog (Cluster Forge / Argo CD) with optional cluster-managed additions (Gitea). Lifecycle rules, version policy, filter vs source removal, and step-by-step procedures are in the Cluster Forge operator guides above — not repeated here.

The packaged baseline is the Cluster Forge in-tree Helm chart sources/aim-cluster-model-source. The AIM team publishes model and base-image lists in aim-build; Platform copies approved snapshots into that chart at each Cluster Forge release.

At install, set AIM_HARDWARE_FAMILY or omit it so cluster-bloom auto-detects from hardware and injects a YAML list into apps.aim-cluster-model-source.valuesObject.hardwareFamilies. A non-empty list uses templates/profiles.yaml (only listed families; the Instinct profile includes generic amd-aim-release-* 0.8.5–0.11.0 plus Instinct 0.11.1+). An empty list ([]) is the chart default and selects templates/unfiltered.yaml: Instinct 0.11.1, 0.12.0, 0.13.0 plus mixed base images. Clearing the list in Gitea after a family-filtered install switches to that unfiltered branch; it does not fail chart rendering.

Before upgrading Cluster Forge, review the incoming packaged catalog and remove cluster-managed manifests that duplicate newly included models or bases. See Before a platform upgrade in the Cluster Forge how-to guide.

CR and chart references#

Topic	Guide
`AIMClusterModelSource` append-only discovery and source deletion	Model Sources (AIM Engine)
Packaged baseline chart (`hardwareFamilies` empty = Instinct 0.11.1+ plus mixed bases)	aim-cluster-model-source README (Cluster Forge `main`)