Artifact Manifest

This section provides a comprehensive list of all components required for NVIDIA Cloud Functions (NVCF) Self-Hosted deployment for basic inference. Additional components are needed for Low Latency Streaming (Simulation).

Artifacts Overview

The following inventories list the artifacts for an inference-only self-hosted NVCF deployment. Artifacts are grouped by deployment plane and type.

Prepare Helm charts for Helmfile

The self-managed Helmfile bundles currently expect NVCF charts in an OCI registry. Chart distributions that start with https:// are Helm repository charts. Before deploying with Helmfile, copy each required repository chart version into the OCI registry configured by global.helm.sources in the Helmfile bundles.

The following example copies one public NVCF chart into an OCI registry:

$
export CHART_NAME="helm-nvcf-api"
$
export CHART_VERSION="1.23.9"
$
export TARGET_REGISTRY="<registry-host>"
$
export TARGET_REPOSITORY="<repository>"
$
$
helm repo add nvcf https://helm.ngc.nvidia.com/nvidia/nvcf
$
helm repo update
$
helm pull "nvcf/${CHART_NAME}" --version "${CHART_VERSION}"
$
$
helm registry login "${TARGET_REGISTRY}"
$
helm push "${CHART_NAME}-${CHART_VERSION}.tgz" \
>
  "oci://${TARGET_REGISTRY}/${TARGET_REPOSITORY}"

Repeat this process for every required chart with an https:// distribution. Copy required charts with an nvcr.io distribution into the same target repository so Helmfile can resolve all NVCF charts from one source. Configure the stack environment with that OCI location:

1
global:
2
  helm:
3
    sources:
4
      registry: "<registry-host>"
5
      repository: "<repository>"

See Image Mirroring for additional registry examples.

Use upstream container images

You can configure a chart to pull a supporting image directly from its upstream registry. For example, replace the nats.reloader.image block in deploy/stacks/self-managed/global.yaml.gotmpl to pull the NATS configuration reloader from Docker Hub:

1
nats:
2
  reloader:
3
    image:
4
      registry: docker.io
5
      repository: natsio/nats-server-config-reloader
6
      tag: "0.23.0"

Use the version listed in the artifact table. Verify that your cluster can reach the upstream registry. If the registry requires authentication, add its pull secret to global.imagePullSecrets.

To pull the API account-bootstrap Kubernetes utilities from their upstream image, replace the api.accountBootstrap.image block in global.yaml.gotmpl:

1
api:
2
  accountBootstrap:
3
    image:
4
      registry: docker.io
5
      repository: alpine/k8s
6
      tag: "1.36.1"

The current Cassandra initialization hook uses the nvcf-cassandra-migrations image, and the current NATS chart renders NKeys as Secrets without an nkey job. Their legacy cassandra.initialization.image and nats.nkeyJob.image values do not control rendered workloads. Using alpine-k8s for those operations requires chart support rather than a configuration-only override.

The following tables list the complete artifact inventory.

Control plane Helm charts

Control plane services and images

Compute plane Helm charts

Compute plane services and images

Tools and deployment resources