'--compute-nodes' Parameter Creates Extra Infra Nodes in a ROSA Cluster

[maulikshah999]

Our team noticed that extra infra nodes are created when we create a ROSA cluster.

Here is the command which is used in our terraform script.

$rosa create cluster --cluster-name='${self.triggers.cluster_name}' --compute-machine-type='${var.worker_machine_type}' --compute-nodes ${var.worker_machine_count} --region ${var.region} \
    --machine-cidr='${var.machine_network_cidr}' --service-cidr='${var.service_network_cidr}' --pod-cidr='${var.cluster_network_cidr}' --host-prefix='${var.cluster_network_host_prefix}' --private=${var.private_cluster} \
    --multi-az=${var.multi_zone} --version='${var.openshift_version}' --subnet-ids='${local.subnet_ids}' --watch

Value used: worker-machine-type="m5.4xlarge" worker-machine-count="6"

Reference link: https://docs.openshift.com/rosa/rosa_cli/rosa-manage-objects-cli.html#rosa-create-cluster_rosa-managing-objects-cli

Expected Behavior: Only selected worker nodes should be created but extra Infra nodes should not be created.

Thanks.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

[nastacio]

This should not be marked as rotten without an answer.

/remove-lifecycle stale /lifecycle frozen

[vkareh]

All ROSA clusters need infra nodes. The instance type of the infra nodes is determine by the number of worker nodes in the cluster.