Closed alita1991 closed 12 months ago
Hi @alita1991, unfortunately this is normal, for the same reason as your previous issue (#142); files can't easily be retrieved from a remote machine with SSH (at least without https://github.com/loafoe/terraform-provider-ssh).
Using generated certificates allows the module to create a valid Kubernetes without retrieving it.
Hi @xunleii, thanks for your quick response, is pretty surprising that terraform does not offer at least the basic functionality like ssh/scp, which is required in many scenarios, including the one where you need to get the logs for debugging purposes.
I guess we can close this ticket for now, and wait until we have support from terraform.
Thanks
I think they made this choice because Terraform is not a "provisioning" tool like Ansible that do things directly on instances but more a tool to interface all cloud/API providers in a same and reproducible manner.
To be honest, this module is a bit "crappy" for Terraform because it uses Terraform like Ansible to install k3s with the power of TF state (and mostly because I don't like Ansible 🙄).
Also, if you already using Ansible, perhaps k3s-ansible may suit your needs better.
Hi,
When provisioning k3s with generate_ca_certificates = false, I noticed that the kubeconfig file is not available anymore. Is there a reason for not exporting it for this particular scenario?
Thanks