garutilorenzo/k3s-aws-terraform-cluster

Deploy an high available K3s cluster on Amazon AWS

k3s-aws-terraform-cluster's Issues

Can't initialize on MacOS M1

Hey
This terraform module looks like exactly what I need!

Although it seems link on of the dependencies, hasicorp/template has been archived and is unavailable for Macos M1
Provider registry.terraform.io/hashicorp/template v2.2.0 does not have a package available for your current platform, darwin_arm64.

How can I setup up Amazon Cloud Provider

I'm just getting started with k3s.
My question is how can I setup this amazon cloud provider using your terraform code.
I followed this doc 👇but could not find the proper solution
https://rancher.com/docs/rancher/v2.5/en/cluster-provisioning/rke-clusters/cloud-providers/amazon/
Can you please explain

k3s agent and addvertise-address

it looks that on agent(worker) node we need cannot use --advertise-address flag anymore

https://docs.k3s.io/kr/cli/agent

The connection to the server localhost:8080 was refused on Master Node 2 & 3

Hi Lorenzo Gauruti,

Thank You sharing the source code for building k3s in AWS using Terraform:
I followed the exact code & built 3 Master & 3 Worker nodes. I can only see one Master node 1:
k3s failed on Master Node 2 & 3:

Any pointers or help will much appreciated:

Master Node1:
root@i-04eb4456e0a425e92:# kubectl get nodes
NAME STATUS ROLES AGE VERSION
i-04eb4456e0a425e92 Ready control-plane,etcd,master 66m v1.24.3+k3s1
root@i-04eb4456e0a425e92:# ls -al /etc/rancher/k3s/k3s.yaml
-rw------- 1 root root 2969 Aug 8 18:51 /etc/rancher/k3s/k3s.yaml

Master Node 2 & 3:
root@i-04b860d791d7a9ebd:~# kubectl get nodes
The connection to the server localhost:8080 was refused - did you specify the right host or port?

cat /var/log/cloud-init-output.log

Created symlink /etc/systemd/system/multi-user.target.wants/k3s.service → /etc/systemd/system/k3s.service.
[INFO] systemd: Starting k3s
Job for k3s.service failed because the control process exited with error code.
See "systemctl status k3s.service" and "journalctl -xeu k3s.service" for details.
k3s did not install correctly

journalctl -xeu k3s:
Aug 08 21:08:09 i-04b860d791d7a9ebd sh[40898]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.se>
Aug 08 21:08:09 i-04b860d791d7a9ebd sh[40899]: Failed to get unit file state for nm-cloud-setup.service:>
Aug 08 21:08:09 i-04b860d791d7a9ebd k3s[40902]: time="2022-08-08T21:08:09Z" level=info msg="Starting k3s>