Goal
Write a conceptual explainer page that gives readers a clear mental model of how NKP is structured, so they can reason about deployments, upgrades, and extension points without diving into code.
Scope
Page lives under docs/docs/explanations/ covering:
- Layered architecture: cloud/bare-metal provider → Kubernetes cluster → foundational software (ingress, cert-manager, Keycloak, ArgoCD, storage) → Nebari Operator → Software Packs → dynamic landing page.
- The
nic CLI: what it does (provisions Kubernetes + foundational layer), what it doesn't do (it is not an application manager).
- GitOps via ArgoCD: how applications and packs are reconciled from Git, not imperatively installed.
- State management: NIC tracks provisioned infrastructure (S3 / Azure Blob / GCS backends) with locking.
- Separation of concerns: platform team vs. pack developer vs. end user; why infrastructure and applications evolve on independent lifecycles.
Out of scope
Acceptance criteria
Resources
Most authoritative (code-audited): AGENTS.md in nebari-infrastructure-core (PR #297).
Repos:
Design docs in nebari-infrastructure-core (some claims may be aspirational and not yet shipped; cross-check against AGENTS.md):
Goal
Write a conceptual explainer page that gives readers a clear mental model of how NKP is structured, so they can reason about deployments, upgrades, and extension points without diving into code.
Scope
Page lives under
docs/docs/explanations/covering:nicCLI: what it does (provisions Kubernetes + foundational layer), what it doesn't do (it is not an application manager).Out of scope
nicCLI command reference (separate sub-issue per [Epic] Rearchitect nebari.dev docs for Nebari Kubernetes Platform (NKP) + Software Packs #621).Acceptance criteria
nicCLI does vs. doesn't do after reading.Resources
Most authoritative (code-audited):
AGENTS.mdinnebari-infrastructure-core(PR #297).Repos:
nicCLIDesign docs in
nebari-infrastructure-core(some claims may be aspirational and not yet shipped; cross-check againstAGENTS.md):