search

k8s-proxmox / cluster-api-provider-proxmox

Cluster API provider implementation for Proxmox VE
Apache License 2.0
95 stars 11 forks source link

kubeadmcontrolplane do not scale up #59

Closed 3deep5me closed 11 months ago

3deep5me commented 11 months ago

/kind bug

What steps did you take and what happened: Do the Quick-Start

The kubeadmcontrolplane do not scale up to 3 replicas with the following warning:

Status:
  Conditions:
    Last Transition Time:  2023-08-02T07:36:41Z
    Message:               Scaling up control plane to 3 replicas (actual 1)
    Reason:                ScalingUp
    Severity:              Warning
    Status:                False
    Type:                  Ready
    Last Transition Time:  2023-08-02T07:39:35Z
    Status:                True
    Type:                  Available
    Last Transition Time:  2023-08-02T07:36:21Z
    Status:                True
    Type:                  CertificatesAvailable
    Last Transition Time:  2023-08-02T07:36:51Z
    Status:                True
    Type:                  MachinesReady
    Last Transition Time:  2023-08-02T07:36:41Z
    Message:               Scaling up control plane to 3 replicas (actual 1)
    Reason:                ScalingUp
    Severity:              Warning
    Status:                False
    Type:                  Resized
  Initialized:             true
  Observed Generation:     1
  Ready:                   true
  Ready Replicas:          1
  Replicas:                1
  Selector:                cluster.x-k8s.io/cluster-name=cappx-test,cluster.x-k8s.io/control-plane
  Unavailable Replicas:    0
  Updated Replicas:        1
Events:
  Type     Reason                 Age                  From
                    Message
  ----     ------                 ----                 ----
                    -------
  Warning  ControlPlaneUnhealthy  44s (x143 over 73m)  kubeadm-control-plane-controller  Waiting for control plane to pass preflight checks to continue reconciliation: Machine cappx-test-qvsbk does not have a corresponding Node yet (Machine.status.nodeRef not set)

What did you expect to happen: The kubeadmcontrolplane scales up to 3 without the error

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Environment:

sp-yduck commented 11 months ago

It's not a bug or something but expected behavior. Because cappx does not initialize the nodes (does not add providerID to nodes), Machines never get Machine.status.nodeRef. Node initialization can be done by CCM so once you deploy CNI and CCM (ccm is applied automatically by clusterresourceset if you are using QuickStart template) to workload cluster, the Machines get nodeRef and then controlplane will scale up.

3deep5me commented 11 months ago

Thank you for your fast reply!