Skip to content

Self-hosted control-plane HA #985

Closed
6 of 6 issues completed
Closed

Description

@shobham-nv

Description

Enable in-cluster high availability for the NVCF self-hosted control plane so a single pod or node failure does not take down API, invocation, messaging or registration.

Delivers one Helmfile highAvailability: profile that turns on:

  • Tier-1 active–active (≥2 Ready replicas with anti-affinity, topology spread, PDB)
  • Tier-2 quorum HA (NATS 3, OpenBao 3, Cassandra 3; multi-AZ uses LOCAL_QUORUM)
  • Docs for AZ labels and dedicated node pools in both AZs
  • Basic failure validation (install shape, pod kill, drain)
  • Preserve single-node / local BDD behavior

Definition of Done

  • highAvailability: schema exists and maps through global.yaml.gotmpl to chart values
  • Production profile install on ≥3 nodes: Tier-1 ≥2 Ready; Tier-2 = 3 Ready on distinct nodes
  • Tier-1 pod kill / node drain does not cause sustained control-plane outage
  • single-node / local BDD path still works
  • Operator docs cover AZ labels, dedicated pools, and short RTO notes

By submitting this issue, you acknowledge that you are an assigned member of the NVCF development team and agree to follow our code of conduct and our contributing guidelines.

Activity

  1. self-assigned this
    on Aug 19, 2026
  2. added theissue type on Aug 19, 2026
  3. shobham-nv commented on Oct 12, 2026

    @shobham-nv
    ContributorAuthor

    Phase 2 (multi-replica grpc-proxy and invocation-service through Envoy) is tracked in #2440.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions