Cluster API MachineDeployment cannot join cluster

[d3bt3ch]

trafficstars

Cluster API MachineDeployment cannot join cluster. Also, when I increase the replica count of the control plane, the cluster is not get provisioned.

Here is the status output

NAME                                                           READY  SEVERITY  REASON                       SINCE  MESSAGE
Cluster/dev-clustr                                             True                                          8h
├─ClusterInfrastructure - AWSCluster/dev-clustr                True                                          8h
├─ControlPlane - KubeadmControlPlane/dev-clustr-control-plane  True                                          8h
│ └─Machine/dev-clustr-control-plane-5ktv6                     True                                          8h
└─Workers
  └─MachineDeployment/dev-clustr-ng-default                    False  Warning   WaitingForAvailableMachines  5m41s  Minimum availability requires 1 replicas, current 0 available
    └─Machine/dev-clustr-ng-default-75b947fd76xnwh9x-kzm5m     True                                          5m8s

Here is the description

Name:         dev-clustr-ng-default
Namespace:    default
Labels:       cluster.x-k8s.io/cluster-name=dev-clustr
Annotations:  machinedeployment.clusters.x-k8s.io/revision: 1
API Version:  cluster.x-k8s.io/v1beta1
Kind:         MachineDeployment
Metadata:
  Creation Timestamp:  2023-07-31T20:26:14Z
  Generation:          1
  Owner References:
    API Version:     cluster.x-k8s.io/v1beta1
    Kind:            Cluster
    Name:            dev-clustr
    UID:             133ec57f-a519-4647-b458-7e7f7f303d14
  Resource Version:  1058081
  UID:               d03046b1-9c29-473a-96f0-17b8709eee80
Spec:
  Cluster Name:               dev-clustr
  Min Ready Seconds:          0
  Progress Deadline Seconds:  600
  Replicas:                   1
  Revision History Limit:     1
  Selector:
    Match Labels:
      cluster.x-k8s.io/cluster-name:     dev-clustr
      cluster.x-k8s.io/deployment-name:  dev-clustr-ng-default
  Strategy:
    Rolling Update:
      Max Surge:        1
      Max Unavailable:  0
    Type:               RollingUpdate
  Template:
    Metadata:
      Labels:
        cluster.x-k8s.io/cluster-name:     dev-clustr
        cluster.x-k8s.io/deployment-name:  dev-clustr-ng-default
    Spec:
      Bootstrap:
        Config Ref:
          API Version:  bootstrap.cluster.x-k8s.io/v1beta1
          Kind:         KubeadmConfigTemplate
          Name:         dev-clustr-ng-default
      Cluster Name:     dev-clustr
      Infrastructure Ref:
        API Version:  infrastructure.cluster.x-k8s.io/v1beta2
        Kind:         AWSMachineTemplate
        Name:         dev-clustr-ng-default
      Version:        v1.27.3
Status:
  Conditions:
    Last Transition Time:  2023-07-31T20:26:14Z
    Message:               Minimum availability requires 1 replicas, current 0 available
    Reason:                WaitingForAvailableMachines
    Severity:              Warning
    Status:                False
    Type:                  Ready
    Last Transition Time:  2023-07-31T20:26:14Z
    Message:               Minimum availability requires 1 replicas, current 0 available
    Reason:                WaitingForAvailableMachines
    Severity:              Warning
    Status:                False
    Type:                  Available
  Observed Generation:     1
  Phase:                   ScalingUp
  Replicas:                1
  Selector:                cluster.x-k8s.io/cluster-name=dev-clustr,cluster.x-k8s.io/deployment-name=dev-clustr-ng-default
  Unavailable Replicas:    1
  Updated Replicas:        1
Events:
  Type    Reason            Age    From                          Message
  ----    ------            ----   ----                          -------
  Normal  SuccessfulCreate  7m34s  machinedeployment-controller  Created MachineSet default/dev-clustr-ng-default-75b947fd76xnwh9x

What did you expect to happen?

The workers would join the cluster

Cluster API version

1.5.0

Kubernetes version

1.27.3

Anything else you would like to add?

No response

Label(s) to be applied

/kind bug One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.