Skip to content
Skills Library
DevOps & cloud · Learning & explanation

nvcf-explore-stack

/nvcf-explore-stack

Navigate and explain the NVCF self-hosted stack inside the monorepo. Maps helmfile releases to their charts, image-source subtrees, helm hooks, namespaces, and `needs:` dependency chains. Reads deploy/stacks/self-managed/helmfile.d/*.yaml.gotmpl and deploy/stacks/nvcf-compute-plane/helmfile.d/*.yaml.gotmpl as the source of truth for ordering and versions. Use when a user or developer asks "what deploys X", "what does X depend on", "what hooks run for X", "walk me through deployment order", "which subtree do I edit to change X", "what namespaces does the stack use", or mentions stack topology,

Repository
nvcf ↗
Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Navigate and explain the NVCF self-hosted stack inside the monorepo. Maps helmfile releases to their charts, image-source subtrees, helm hooks, namespaces, and `needs:` dependency chains. Reads deploy/stacks/self-managed/helmfile.d/*.yaml.gotmpl and deploy/stacks/nvcf-compute-plane/helmfile.d/*.yaml.gotmpl as the source of truth for ordering and versions. Use when a user or developer asks "what deploys X", "what does X depend on", "what hooks run for X", "walk me through deployment order", "which subtree do I edit to change X", "what namespaces does the stack use", or mentions stack topology,

Triggers from the description

what deploys Xwhat does X depend onwhat hooks run for Xwalk me through deployment orderwhich subtree do I edit to change Xwhat namespaces does the stack use
Original author description

Navigate and explain the NVCF self-hosted stack inside the monorepo. Maps helmfile releases to their charts, image-source subtrees, helm hooks, namespaces, and `needs:` dependency chains. Reads deploy/stacks/self-managed/helmfile.d/*.yaml.gotmpl and deploy/stacks/nvcf-compute-plane/helmfile.d/*.yaml.gotmpl as the source of truth for ordering and versions. Use when a user or developer asks "what deploys X", "what does X depend on", "what hooks run for X", "walk me through deployment order", "which subtree do I edit to change X", "what namespaces does the stack use", or mentions stack topology,

How it works

  1. Instructions
  2. Required inputs
  3. Common questions
  4. Subtree mapping
  5. Tone
  6. Skill handoff candidates
Original SKILL.md headings · 80 lines, 647 words
SKILL.md preview
---
name: nvcf-explore-stack
description: >-
  Navigate and explain the NVCF self-hosted stack inside the monorepo. Maps
  helmfile releases to their charts, image-source subtrees, helm hooks,
  namespaces, and `needs:` dependency chains. Reads
  deploy/stacks/self-managed/helmfile.d/*.yaml.gotmpl and
  deploy/stacks/nvcf-compute-plane/helmfile.d/*.yaml.gotmpl as the source of
  truth for ordering and versions.
  Use when a user or developer asks "what deploys X", "what does X depend
  on", "what hooks run for X", "walk me through deployment order", "which
  subtree do I edit to change X", "what namespaces does the stack use", or
  mentions stack topology, helmfile stages, deployment DAG, or dependency map.
license: Apache-2.0
compatibility: Requires a local checkout of the NVCF monorepo with deploy/stacks/self-managed/ and deploy/stacks/nvcf-compute-plane/ present
author: "nvcf-core-eng <nvcf-core-eng@exchange.nvidia.com>"
version: "1.1.2"
tags: [nvcf, self-managed, self-hosted, helmfile, deployment, stack-topology]
tools: [Read, Grep, Glob]
metadata:
  internal: false
  author: "nvcf-core-eng <nvcf-core-eng@exchange.nvidia.com>"
  version: "1.1.2"
  tags: [nvcf, self-managed, self-hosted, helmfile, deployment, stack-topology, dependencies, hooks]
  languages: [yaml, markdown]
  frameworks: [helmfile, helm, kubernetes]
  domain: cloud-infrastructure
---

# NVCF Explore Stack

Help a user or developer navigate the NVCF self-hosted stack inside the monorepo. Identify what a release is, what installs it, what it depends on, and which subtree owns the chart and the runtime image.

## Instructions

This skill is for both NVCF users and NVCF developers. Users use it to understand stack dependencies, deployment order, and CI/CD migration questions. Developers use it to find the owning chart, source subtree, hook, or helmfile stage before making changes.

Use this skill long enough to answer the question, then hand off to the right execution skill. Always cite the source file path so the user can verify.

## Required inputs

Read these from the monorepo root.

Authoritative (always read first when answering):

- `deploy/stacks/self-managed/helmfile.d/00-observability-infrastructure.yaml.gotmpl`
- `deploy/stacks/self-managed/helmfile.d/01-dependencies.yaml.gotmpl`
- `deploy/stacks/self-managed/helmfile.d/02-core.yaml.gotmpl`
- `deploy/stacks/self-managed/helmfile.d/03-observability.yaml.gotmpl`
- `deploy/stacks/observability/helmfile.d/01-observability.yaml.gotmpl`
- `deploy/stacks/nvcf-compute-plane/helmfile.d/01-dependencies.yaml.gotmpl`
- `deploy/stacks/nvcf-compute-plane/helmfile.d/02-nvca.yaml.gotmpl`

Chart-level (when the chart is checked into the monorepo):

- `deploy/helm/<chart>/Chart.yaml`
- `deploy/helm/<chart>/values.yaml`

## Common questions

What deploys X
: Look up release `X` in the helmfile stage files. Return chart name, version, namespace, and which gotmpl file declares it. If the chart is checked in, also point at `deploy/helm/<chart>/`.

What does X depend on
: Return the `needs:` chain for that release plus the stage gate it sits behind (control-plane stages 0 -> 1 -> 2 -> 3, then compute-plane). Include any profile, `condition:`, or component mode that gates whether X deploys at all.

What hooks run for X
: Read the checked-in chart under `deploy/helm/<chart>/` when available. Search its `templates/` directory for Helm hook annotations, weights, hook events (pre-install / post-install), images used, and purpose. Cite the chart-relative template file path. If the chart is not checked in, cite its Helmfile chart reference and state that local templates are unavailable.

Walk me through the full deployment order
: Summarize control-plane stages 0 through 3 from the self-managed gotmpl files. Stage 0 delegates to the shared observability Helmfile when `observability.profile` is enabled. Stage 3 installs State Metrics and the function autoscaler for `control` and `all`. Then summarize the compute-plane stage from `deploy/stacks/nvcf-compute-plane/helmfile.d/01-dependencies.yaml.gotmpl` and `deploy/stacks/nvcf-compute-plane/helmfile.d/02-nvca.yaml.gotmpl`. Call out which releases run in parallel inside a stage and which are serialized by `needs:`.

Which subtree do I edit to change X
: Point at the Helmfile path for orchestration, `deploy/helm/<chart>/` for checked-in chart wiring, and the image source under `src/`, `infra/`, or `migrations/` for runtime behavior. If a referenced chart is not checked in, report its Helmfile chart reference and do not claim a local source path.

What namespaces does the stack use
: Return the list from the helmfile (`namespace:` per release).

## Subtree mapping

The stack lives in three layers across the monorepo:

| Concern | Lives at |
|---------|----------|
| Helmfile orchestration (stage ordering, env wiring, secrets flow) | `deploy/stacks/self-managed/` |
| Chart manifests, helm hooks, values | `deploy/helm/<chart>/` when checked in; otherwise use the Helmfile chart reference |
| Runtime application code, migrations | `src/`, `infra/`, `migrations/` |

When a question crosses layers, answer by layer and tell the user the order to edit (chart wiring first if the deploy contract changes, image source if behavior changes).

## Tone

Assume the user is onboarding to the stack. Be concise. Always include the chart name, version, and the gotmpl path when referencing a release. Prefer one short paragraph plus a code-block citation over prose.

## Skill handoff candidates

After exploring, suggest the next skill when applicable:

- `nvcf-self-managed-installation` for installing, upgrading, or tearing down the stack
- `docs/dev/local-development.md` for k3d / local cluster work
- `nvcf-self-managed-cli` for `nvcf-cli` usage against an installed stack
- `docs/AGENTS.md`, `fern/navigation.yml` (current tabs), and `fern/docs.yml`
  (release selector and archives) for routing the user to a published docs page
- `docs/dev/docs-editions.md` for legacy immutable docs editions
- `docs/dev/umbrella-releases.md` for qualified product bundles and maintained
  `docs/versions/X.Y.Z` sources selected by approved commit
- `tools/ci/check-doc-version-sync` for keeping the documentation manifest in sync with the docs version catalog

Versions

The database has no other skills named nvcf-explore-stack.

Database snapshot: 13.11.2026 · package version 2a5cf510123f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100nvcf-self-managed-installation
    Install and operate NVCF self-hosted control-plane and separate compute-plane stacks. Covers Helmfile values and CLI profile installation flows, teardown, values overrides, pull secrets, and troubleshooting. Use for nvcf-self-managed-stack, nvcf-compute-plane-stack, split…
  • 100nvca-self-managed-install
    Install or validate the NVCA Operator chart against a self-managed NVCF control plane from the native monorepo. Use when the control plane comes from deploy/stacks/self-managed and NVCA must be installed with stack-derived image repository settings.
  • 100helm
    Expert coverage of the Helm package manager (Helm 3 and Helm 4): chart development, Go templates, values, hooks, OCI registries, SSA, Helmfile, helm-secrets, and dependency management. Use for \"Helm\", \"Helm chart\", \"helm install\", \"helm template\", \"Helmfile\",…
  • 100helm-charts
    Expert guidance for authoring and maintaining Helm charts following standardized conventions, global registry support, templating best practices, and Kubernetes deployment patterns. Use this skill when creating new Helm charts, reviewing or modifying existing charts, configuring…
  • 95helm-patterns
    Use this skill when the user says 'helm', 'helm chart', 'helm template', 'helm install', 'helm upgrade', 'helm rollback', 'helmfile', 'helm secrets', 'helm values', 'helm dependency', 'helm repository', 'helm plugin', 'helm unittest', 'helm lint', 'helm package', 'helm…
  • 100helm-charts
    Create, manage, and deploy Helm charts for Kubernetes package management. Build reusable chart templates, manage releases, configure values, and use Helm repositories. Use when packaging Kubernetes applications or managing K8s deployments with Helm.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.