skilld
All skills
nvidia avatar

/physical-ai-infrastructure-setup-and-resilient-scaling

@6c6fc09
by NVIDIA Corporationnvidia/skills3.5k stars
424

Use when the user wants to set up, scale, validate, or harden NVIDIA physical AI infrastructure for synthetic data generation workflows across local MicroK8s or Azure AKS, including Kubernetes clusters, inference endpoint deployment, OSMO deployment, workload submission readiness, and infrastructure failure recovery. Trigger keywords: physical ai infrastructure, resilient scaling, SDG infrastructure, microk8s, azure aks, NVCF deployment, NIM Operator, OSMO deploy, workflow scaling. Don't trigger for: OSMO log summarization or workload-only operations unless infrastructure setup, scaling, validation, or recovery is requested.

Ask your Agent

Use this Skill: https://skilld.dev/gh/nvidia/skills/physical-ai-infrastructure-setup-and-resilient-scaling

This session only. Nothing lands on disk.

componentsosmo-k8sreference.md

≈630 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Kubernetes OSMO

Prerequisites

Supporting files

Path Use When
scripts/preflight.sh Run first Checks local MicroK8s/Kubernetes tools, Helm, Git, and repo .env; cluster state is verified during deploy.

Deployment

  1. Run preflight
REPO="$(git rev-parse --show-toplevel)"
"$REPO/skills/physical-ai-infrastructure-setup-and-resilient-scaling/components/osmo-k8s/scripts/preflight.sh"
  1. Clone https://github.com/nvidia/osmo - use main unless otherwise specified
OSMO_REF="${OSMO_REF:-main}"
OSMO_DIR="$HOME/.cache/physical-ai/osmo"
if [ -d "$OSMO_DIR/.git" ]; then
  git -C "$OSMO_DIR" fetch --depth 1 origin "$OSMO_REF"
  git -C "$OSMO_DIR" reset --hard FETCH_HEAD
else
  mkdir -p "$(dirname "$OSMO_DIR")"
  git clone --depth 1 --branch "$OSMO_REF" \
    https://github.com/NVIDIA/OSMO.git "$OSMO_DIR"
fi
  1. Load environment secrets
REPO="$(git rev-parse --show-toplevel)"
[ -f "$REPO/.env" ] && { set -a; . "$REPO/.env"; set +a; }
  1. Check for an existing OSMO install before deploying. Do not redeploy or upgrade a working install just because namespace osmo is empty; Physical AI infra uses the osmo-minimal namespace.
helm status -n osmo-minimal osmo-minimal
kubectl get pods -n osmo-minimal
osmo workflow list --count 5

If Helm status succeeds and the pods are healthy, reuse the existing install. Only continue to deploy when OSMO is absent or the user explicitly approves a repair/redeploy.

  1. Deploy OSMO in "minimal" configuration in MicroK8s mode with in-cluster PostgreSQL, Redis, MicroK8s MinIO add-on, ClusterIP gateway with port-forward watchdog
"$OSMO_DIR/deployments/scripts/deploy-osmo-minimal.sh" \
  --provider microk8s \
  --storage-backend minio \
  --non-interactive

For CPU-only instances, add --no-gpu.

Verify

Verification is done as part of deploy-osmo-minimal.sh. If the script exits with exit code 0, the OSMO deployment is considered verified.

Re-run

Do not re-run deployment scripts during demos without explicit user approval. Use the existing-install checks above first.

Cleanup

This intentionally only cleans up the OSMO install - the MicroK8s cluster remains up.

pkill -f 'osmo-pf-watchdog:' || true
$OSMO_DIR/deployments/scripts/deploy-osmo-minimal.sh \
  --provider microk8s \
  --destroy --non-interactive

Source: SKILL.md on GitHub

Third-party checks

2 warnings3mo3 checks · Risk SAFE
  • Gen Agent Trust Hub3mo

    This skill from NVIDIA provides a comprehensive set of tools and instructions for setting up Physical AI infrastructure on Azure AKS or local MicroK8s clusters. The analysis found no malicious patterns; all external downloads are from trusted or well-known services (NVIDIA, Microsoft, HashiCorp, Hugging Face), and the orchestration design prioritizes user visibility through a partitioned multi-agent architecture.

  • Socket3mo

    1 alert: gptAnomaly

  • Snyk3mo

    Risk: MEDIUM · 1 issue

Provenance

Signed by skilld at 6c6fc09. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 4 months ago

Capability

version
1.0.0
tools
[
  "Read",
  "Shell"
]
Other metadata
compatibility
Requires the selected component prerequisites, usually kubectl plus either MicroK8s or Azure CLI/Terraform, and OSMO or inference credentials for the chosen target.
metadata
{
  "author": "NVIDIA Physical AI",
  "tags": [
    "physical-ai",
    "infrastructure",
    "kubernetes",
    "azure",
    "microk8s",
    "osmo",
    "nim-operator",
    "scaling"
  ],
  "domain": "ai-ml",
  "languages": [
    "bash",
    "hcl",
    "yaml"
  ]
}

README badge

README badge for nvidia/skills/physical-ai-infrastructure-setup-and-resilient-scaling