Skip to content

v0.0.1

Choose a tag to compare

@anandj91 anandj91 released this 04 Sep 18:01
58746da

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 CD AppProject per namespace,
    restricted to the catalog repository, and mirrors the Secret named by
    spec.clusterCredentialsRef into 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
    Application in 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.conditions as Validated, ComponentsApplied and Progressing. The
    controller starts and reports ApplicationCRDMissing when 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 what CCLComponentSet component chart
    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_base chart's Helm values as typed structs,
    under github.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_agent validates its required
    values rather than installing an agent that cannot connect. These are a convenience for
    Go callers, not a validation layer: the CRD's values field remains untyped.
  • ccluster-py, a generated Pydantic v2 rendering of the CRDs and of every catalog
    component's values, published to PyPI. Regenerated by make python-generate; CI fails
    on drift from the Go types.
  • Helm charts ccluster-cp and ccluster-ip for the two operators, generated from the
    kustomize overlays by the kubebuilder helm/v2-alpha plugin and published to
    oci://ghcr.io/nvidia/charts. make deploy-cp / deploy-ip install 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 by make deploy-cp and never by the operator itself. Skip it with
    make deploy-cp ARGOCD=false; bump it with make helm-deps-update-cp. The bundled
    application controller runs with controller.diff.server.side to match the
    ServerSideApply sync 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 by make install over to the Helm
    release without deleting anything.
  • Release pipeline. Every merge to main publishes 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.Z that updates this file and the root VERSION
    file, followed by a GitHub Release on its merge commit, which retags the images as
    X.Y.Z, re-packages the charts, publishes ccluster-py==X.Y.Z to PyPI and attaches
    the assets. The workflow refuses a tag that disagrees with VERSION, and PRs carrying
    the release label 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-e2e deploys with ARGOCD=false into a
    disposable kind cluster and covers RBAC, watch wiring and the status paths reachable
    without Argo CD; make test-e2e-full upgrades the same release to real Argo CD and
    proves ordered release, reverse teardown, selfHeal drift 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 CD ApplicationSet generators and the RollingSync strategy.
  • Legacy catalog package: Helm charts paired with typed Pydantic value schemas for the
    cluster base components and the workload charts inference_deployment_v3,
    cserve_deployment_v3, compute_deployment, job_deployment and namespace_base.
    Being retired in favour of catalogs/ and ccluster-py.
  • Community-health files (Code of Conduct, Contributing, Security, Support, Maintainers).