Jake Hyde

@heinrich-redislabs The file in `/etc/rancher/rke2/config.yaml.d/50-rancher.yaml` is notably missing the `kube-apiserver-arg` argument. Looking at your previous comment, it appears it was mispelled: ``` - config: disable-cloud-controller: true kube-controller-manager-arg: - cloud-provider=external kubeapi-server-arg:...

@heinrich-redislabs If the reported error message is `Waiting for cluster agent to connect`, that indicates to me that the issue is not necessarily with provisioning of the cluster, but rather...

Ah thank you, I can see that some things I would expect to be running are missing, can you try the following? ``` KUBECONFIG=/etc/rancher/rke2/rke2.yaml /var/lib/rancher/rke2/bin/kubectl ``` this will allow you...

If you could also share the `Amazonec2Config` associated with the pools, that would be helpful. For example (in the local cluster): ``` kubectl get -n fleet-default Amazonec2Config nc-test18787164-controlplane-ec2-config -o yaml...

Ah okay, ` Warning FailedScheduling 17m (x11 over 67m) default-scheduler 0/1 nodes are available: 1 node(s) had untolerated taint {node.cloudprovider.kubernetes.io/uninitialized: true}. preemption: 0/1 nodes are available: 1 Preemption is not...

> We've been able to replicate this. We found a workaround in our testing, in that the control-plane pool _requires_ a worker role attached to them during creation. You cannot...

@heinrich-redislabs Still working on an automated healthchecking script, would you be willing to share the output of the following command: `aws ec2 describe-instances --region --filters 'Name=tag:Name,Values='` (redacting any information deemed...

@heinrich-redislabs I think given the context of your [previous comment](https://github.com/rancher/rancher/issues/43891#issuecomment-1876979138), and reviewing the tags, it seems likely that there is an issue regarding the tags. If the tag changes have...

@zaggash Loadbalancers are not currently implemented as part of our v2 provisioning framework. However, loadbalancers would be the correct way to solve this issue.

Closing this issue as rancher has migrated away from using the killall script.