Repository navigation
v0.0.1
First release. Everything below is new; the entries that described intermediate states
of the unreleased tree (the CCLDeployment to CCLComponentSet rename, the move from
kustomize to Helm deploy targets, and fixes to code that never shipped) are folded into
the description of what ships.
Added
CCLInfraPlane(ccluster.nvidia.com/v1alpha1), which registers an infra-plane cluster
with Argo CD. The control-plane operator creates one Argo CDAppProjectper namespace,
restricted to the catalog repository, and mirrors the Secret named by
spec.clusterCredentialsRefinto the Argo CD namespace as a project-scoped cluster
Secret named<namespace>-<name>. The project is removed by the last CCLInfraPlane in
the namespace.CCLComponentSet(ccluster.nvidia.com/v1alpha1), which rolls out an ordered bundle of
catalog charts onto registered clusters. Each component becomes one Argo CD
Applicationin the CCLComponentSet's own namespace under that namespace's project; a
component's Application is not created until every component before it reports Healthy
and Synced, and teardown runs in reverse, one at a time. Progress is reported on
status.conditionsasValidated,ComponentsAppliedandProgressing. The
controller starts and reportsApplicationCRDMissingwhen Argo CD is not installed,
and picks up the Application watch on restart once it is.catalogs/cluster_base, a pure-Helm catalog of 18 platform components (Istio,
cert-manager, SPIRE, KEDA, GPU Operator, kube-prometheus-stack, Longhorn, external-dns,
Fluent Bit, Argo Rollouts and more), which is whatCCLComponentSetcomponentchart
paths resolve against. The repository and revision are operator configuration
(--catalog-repo-url,--catalog-revision), settable at deploy time with
make deploy-cp CATALOG_REPO_URL=... CATALOG_REVISION=....- Go packages describing each
catalogs/cluster_basechart's Helm values as typed structs,
undergithub.com/NVIDIA/ccluster/catalogs/.... Each exports
New(namespace, values) (v1alpha1.ComponentEntry, error), building the API type
directly;catalogs/cluster_base.Components(infraPlane)returns a sample set of all
eighteen in rollout order to copy and edit.teleport_kube_agentvalidates its required
values rather than installing an agent that cannot connect. These are a convenience for
Go callers, not a validation layer: the CRD'svaluesfield remains untyped. ccluster-py, a generated Pydantic v2 rendering of the CRDs and of every catalog
component's values, published to PyPI. Regenerated bymake python-generate; CI fails
on drift from the Go types.- Helm charts
ccluster-cpandccluster-ipfor the two operators, generated from the
kustomize overlays by the kubebuilderhelm/v2-alphaplugin and published to
oci://ghcr.io/nvidia/charts.make deploy-cp/deploy-ipinstall them with
helm upgrade --install;make undeploy-*uninstalls but keeps the CRDs
(helm.sh/resource-policy: keep), so custom resources survive. - Argo CD as a pinned dependency of the control-plane chart, installed alongside the
operator bymake deploy-cpand never by the operator itself. Skip it with
make deploy-cp ARGOCD=false; bump it withmake helm-deps-update-cp. The bundled
application controller runs withcontroller.diff.server.sideto match the
ServerSideApplysync option on every generated Application, so charts with very large
CRDs converge instead of reporting OutOfSync forever. make helm-adopt-crds-cp, which hands CRDs applied bymake installover to the Helm
release without deleting anything.- Release pipeline. Every merge to
mainpublishes both operator images (:<sha>) and
both charts (0.0.0-g<sha>) to GHCR. A release is a reviewed PR titled
release: new ccluster version vX.Y.Zthat updates this file and the rootVERSION
file, followed by a GitHub Release on its merge commit, which retags the images as
X.Y.Z, re-packages the charts, publishesccluster-py==X.Y.Zto PyPI and attaches
the assets. The workflow refuses a tag that disagrees withVERSION, and PRs carrying
thereleaselabel run the full e2e tier in CI. - Agent skills under
.agents/skills/(commit-pr,release,pr-review) that write
down the commit, release and review procedures for any coding agent;.claude/skills
symlinks to the same directory. - Two-tier end-to-end suite.
make test-e2edeploys withARGOCD=falseinto a
disposable kind cluster and covers RBAC, watch wiring and the status paths reachable
without Argo CD;make test-e2e-fullupgrades the same release to real Argo CD and
proves ordered release, reverse teardown,selfHealdrift correction, a values change
rolling forward, and the AppProject as a tenancy boundary. DESIGN.md, describing the control-plane design and the alternatives rejected along
the way, notably Argo CDApplicationSetgenerators and theRollingSyncstrategy.- Legacy
catalogpackage: Helm charts paired with typed Pydantic value schemas for the
cluster base components and the workload chartsinference_deployment_v3,
cserve_deployment_v3,compute_deployment,job_deploymentandnamespace_base.
Being retired in favour ofcatalogs/andccluster-py. - Community-health files (Code of Conduct, Contributing, Security, Support, Maintainers).