Skip to content

Allow control plane machine count to be set per cluster#587

Open
mgrzybek wants to merge 4 commits into
mainfrom
feat/cp-number
Open

Allow control plane machine count to be set per cluster#587
mgrzybek wants to merge 4 commits into
mainfrom
feat/cp-number

Conversation

@mgrzybek

Copy link
Copy Markdown
Contributor

Add an optional controlPlaneMachineCount field to ClusterSpec. When set, it overrides the controlPlane.machineCount defined in the cluster template, enabling operators to choose between a single-node and a 3-node HA control plane at cluster creation time.

Clusters that do not specify this field continue to use the count defined in their template, preserving backwards compatibility.

@mgrzybek
mgrzybek requested a review from a team as a code owner April 15, 2026 09:22
mgrzybek added a commit to azimuth-cloud/azimuth that referenced this pull request Apr 15, 2026
Allow users to choose between 1 (single) or 3 (HA, default) control
plane nodes when creating a Kubernetes cluster.

- API: add `control_plane_count` field (choices: 1 or 3, default: 3)
  to `CreateKubernetesClusterSerializer` and propagate it through
  `create_cluster()` and `_build_cluster_spec()` as
  `controlPlaneMachineCount` in the CRD spec
- Quota calculator: accept an explicit `control_plane_count` that
  overrides the template value when calculating required resources
- UI: add inline radio buttons (1 / 3 HA) after the control plane size
  selector; defaults to 3 on new clusters

Requires azimuth-capi-operator with azimuth-cloud/azimuth-capi-operator#587 merged and released.
@mgrzybek mgrzybek added the enhancement New feature or request label Apr 15, 2026
Comment thread azimuth_capi/templates/cluster-values.yaml
mgrzybek added 4 commits May 13, 2026 10:55
Add an optional `controlPlaneMachineCount` field to `ClusterSpec`.
When set, it overrides the `controlPlane.machineCount` defined in the
cluster template, enabling operators to choose between a single-node
and a 3-node HA control plane at cluster creation time.

Clusters that do not specify this field continue to use the count
defined in their template, preserving backwards compatibility.
Signed-off-by: Mathieu Grzybek <mathieu@stackhpc.com>

@wtripp180901 wtripp180901 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants