This message was deleted.
# general
a
This message was deleted.
b
What cloud provider?
You shouldn't need any of the Rancher manifests to connect downstream clusters to Rancher. In fact, if Rancher can't connect to the downstream cluster then provisioning will fail. You do need to retrieve the kubeconfig of the downstream cluster to connect to it directly, but Rancher also works as a proxy to the downstream clusters and will forward traffic for you by default.
b
We also have a rather bitty way of making new clusters: Terraform to make the VMware instances, another Terraform run to build the cluster on the "local" management (putting VMware as the cloud in a custom installation), manually grabbing the registration script and running it on each instance, more Terraform for setting up egress and ingress... Some parts could be thrown together with an orchestrator, but the registration script is a key blocker to that. If that's the same issue @delightful-gigabyte-66989 has, we aren't alone with this and it would be good to have a way around the registration script portion. Is that possible?
b
Any interest in a module that uses local execs and a custom file provider to orchestrate Terraform within Terraform?
Any interest in a provider that might do something like that? Maybe "terraform-provider-terraform" or something?
The registration script you are referring to is the script that Rancher puts in the cloud-init when deploying downstream cluster nodes, right?
Where are you getting the registration script?
b
It's the system-agent-install.sh script that comes under Cluster Management -> Cluster -> Registration. The Terraform we use for creating the cluster doesn't touch the cluster servers at all. We already use local exec for various parts of Terraform, calling on Ansible for provisioning, but there's no interaction between the different Terraform components.
b
I'm not sure about getting the script from the Rancher API, I will look into that further, but I think I found the codebase for it: https://github.com/rancher/system-agent/blob/7370d98d969c9bc0be248a802c816d3013264ce6/install.sh
It doesn't appear to change that much, last change was 2 months ago and before that several years.
If that is the script you are looking for, you may be able to download it from the repo directly and fill in the gaps for your servers instead of pulling it from Rancher.