launch-nemo-rl

Launch and manage NeMo-RL experiments on Kubernetes with the nrl-k8s CLI.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/sayalinvidia/sayali-skills-test --skill launch-nemo-rl-sayalinvidia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: launch-nemo-rl
Source: https://github.com/sayalinvidia/sayali-skills-test/tree/main/skills/launch-nemo-rl
Command: npx skills add https://github.com/sayalinvidia/sayali-skills-test --skill launch-nemo-rl-sayalinvidia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

NeMo-RL workflows on Kubernetes are complex to orchestrate; this playbook provides a repeatable approach to launching, monitoring, stopping, and debugging NeMo-RL experiments via the nrl-k8s CLI.

Core Features & Use Cases

  • Ephemeral vs long-lived modes to support one-off experiments or iterative development.
  • End-to-end workflow covering recipe submission, status monitoring, log access, and teardown.
  • Use Case: teams deploying NeMo-RL on Kubernetes with governance and reproducibility.

Quick Start

Execute a single command to launch a NeMo-RL recipe on Kubernetes and begin iterative monitoring.

Frequently Asked Questions about launch-nemo-rl

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I launch NeMo-RL training workflows on Kubernetes?

To launch NeMo-RL training on Kubernetes, use the nrl-k8s CLI to submit an infra YAML recipe pair. You can execute a single command to start an experiment and begin iterative monitoring immediately.

What is the difference between ephemeral and long-lived NeMo-RL run modes?

Ephemeral mode supports one-off NeMo-RL experiments, while long-lived mode enables iterative development. Both modes manage the RayCluster lifecycle and allow you to monitor status, retrieve logs, and debug training jobs.

Do I need kubectl to monitor NeMo-RL experiments on a Kubernetes cluster?

Yes, kubectl-based observability is supported for monitoring NeMo-RL experiments on Kubernetes. You need access to a Kubernetes cluster, an infra YAML pair for recipes, and the nrl-k8s CLI to manage and observe RayCluster resources.

How do I debug hung or failed NeMo-RL training jobs on Kubernetes?

Debug hung or failed NeMo-RL training jobs by retrieving logs and checking status through the nrl-k8s CLI. The playbook covers end-to-end debugging, including stopping, tearing down, and iterating on failed RayCluster resources.

What's the best way to manage RayCluster lifecycle for NeMo-RL experiments?

The best way to manage the RayCluster lifecycle is using the nrl-k8s CLI on Kubernetes. It provides a repeatable approach to submit recipes, monitor training status, access logs, and tear down RayCluster resources after experiments.

Why does my NeMo-RL workflow require an infra YAML pair for Kubernetes deployment?

An infra YAML pair is required for Kubernetes deployment to define the NeMo-RL recipe configuration. It provides the necessary specifications for the nrl-k8s CLI to orchestrate RayCluster resources, ensuring reproducibility and governance for teams.