Skip to content
Browse Stacks

Starting questions

Deep Dives

AI: Claude and Codex patterns

ConfigHub: Deploy and manage

Stacks

A stack is a set of charts and YAML named in one manifest and checked for conflicts before it renders. A platform is what a stack becomes once it runs under governance with your apps on it.

Compose and check a stack shows how, step by step. To build your own from Catalog entries, follow Make a stack from Catalog entries, which composes three NVIDIA GPU entries.

New to cub? Install the cub CLI first. Public catalog packages pull and render anonymously, and you sign in only once a command saves or changes ConfigHub data.

Every shipped stack

Stack, and the command to try itWhat it buildsParts
app-platform
cub stack check app-platform
A full platform for a web application: database, cache, ingress, certificates, and monitoring. The shape a Spring Boot app lands on.cert-manager, ingress-nginx, postgresql, redis, kube-prometheus-stack. Every part has a receipt.
data-services
cub stack check data-services
A stateful data tier: cache, relational database, and message queue.redis, postgresql, rabbitmq. Every part has a receipt.
eks-inference
cub stack check eks-inference
The EKS inference platform as a stack: eight digest-pinned certified bundles across three planes. The keystone, spoken in the settled vocabulary. Try NVIDIA AICR for GPUs.platform-profile, ack-controllers, aws-network, eks-cluster, karpenter-aws, karpenter, gpu-runtime, inference-workloads. Every part has a receipt.
gitops-secrets
cub stack check gitops-secrets
A delivery control plane: Argo CD, External Secrets, and cert-manager, three CRD-shipping components composed together.cert-manager, external-secrets, argo-cd. Every part has a receipt.
gpu-node
cub stack check gpu-node
A static composition of NVIDIA's GPU Operator, NVSentinel, and cluster-readiness-engine from the catalog's published bundles, where nothing runs on a GPU and the chart hooks are recorded as declared and not run.gpu-operator, nvsentinel, cluster-readiness-engine. Every part has a receipt.
kubara-gitops-shop
cub stack check kubara-gitops-shop
Kubara components plus the retained Argo CD controller and shop app. Static composition only; repository binding, target prerequisites and live delivery remain required.cert-manager, traefik, metrics-server, external-secrets, argo-cd, shop-web. Not every part has a receipt.
kubara-platform
cub stack check kubara-platform
A small platform of cert-manager, Traefik, and metrics-server, composed from the catalog's published certified bundles.cert-manager, traefik, metrics-server. Every part has a receipt.
kubara-shop-platform
cub stack check kubara-shop-platform
The Kubara platform grown to what the shop app needs: cert-manager, Traefik, metrics-server, and external-secrets, with the app adapted to it: Traefik's ingress class and a secret pulled through external-secrets.cert-manager, traefik, metrics-server, external-secrets, shop-web. Not every part has a receipt.
observability-base
cub stack check observability-base
A base observability platform: certificates, cluster metrics, and the Prometheus stack.cert-manager, metrics-server, kube-prometheus-stack. Every part has a receipt.
redis-platform
cub stack check redis-platform
A managed Redis platform: the cache, its secrets, and monitoring. After the redis-platform pattern in confighub/examples.redis, external-secrets, kube-prometheus-stack. Every part has a receipt.
shop-platform
cub stack check shop-platform
A web platform with monitoring and a message queue, with the shop app running on it: ingress, certificates, the Prometheus stack, RabbitMQ, and shop-web.cert-manager, ingress-nginx, kube-prometheus-stack, rabbitmq, shop-web. Not every part has a receipt.
web-platform
cub stack check web-platform
A platform for web apps: ingress, certificates, and monitoring. Carries exactly what an app like shop-web depends on.cert-manager, ingress-nginx, kube-prometheus-stack. Every part has a receipt.

The stacks made to be refused, to show the check, are in the Guide.