This message was deleted.
# rke2
a
This message was deleted.
m
I assume you could do it easily enough with cloud-init by setting the agent node token in an env var and running the RKE2 installer with --server to your control plane api. You may want to add ssh key access from your bastion host, etc, too.
s
Thanks for the reply.... I have spun up a new server using the same AMI (keys are in there already) However....this is just to add more "worker" nodes to the cluster for auto scaling. When I run the command to install RKE2, that goes fine. I see the node adding into the cluster, but then it just goes away?
I can't be the only one out there that needs more server int he RKE2 cluster???
m
Is it possible that it's automatically downscaling it because you don't have enough load? In that case, the ASG is just doing its job.
You could test it by deploying JupyterHub with a bunch of placeholders or scaling up a bunch of pods
s
I wish it was related to ASG......I still can not get a good operation for ASG running (cluster-autoscaler). This was just to SEE if I can actually get a server to join the cluster on a "manual" process at first.
Im prepping to get the clusters to auto scale....
thanks for the help!
j
s
thanks....Ill check it out.....