Skip to content

Building a Software Pack

Updated 1 min read

This guide covers Nebari Software Packs: what they are, how to build one, and how to maintain it.

A software pack is a Kubernetes application bundled with a NebariApp custom resource. When you deploy one, the Nebari platform automatically wires it into the shared routing, TLS, and OIDC authentication systems - no manual gateway or certificate configuration required.

In this guide

Section titled “In this guide”
  • What is a software pack - definition, why packs exist, pack contents, the NebariApp resource, pack lifecycle, and official vs community packs
  • Build your own - start from the template, choose an example, deploy via ArgoCD, private and organizational packs

Reference pages

Section titled “Reference pages”
  • NebariApp CRD reference - where the generated NebariApp field reference lives, and how to declare one with YAML, Kustomize, or Helm
  • Authentication flow - how OIDC works end-to-end; verifying the IdToken in your app
  • Release readiness - maturity levels and the promotion checklist for first-party packs

Pack template

Section titled “Pack template”

Use the software-pack-template as your starting point. It includes five examples spanning plain YAML, Kustomize, basic Helm, auth-aware apps, and wrapping an existing upstream chart.