This message was deleted.
# amazon
a
This message was deleted.
f
Curious to know if you managed to get it work
c
@flaky-kilobyte-53977 where k3s is fully managing the ALB or where the ALB is tracking the k3s instances and routing all traffic to nginx for processing?
f
@colossal-dentist-5939 any of these two would suffice
i am not sure if former will ever be possible i.e kubctl create -f <ingress.yaml> and it will dynamically an AWS ALB and upon deleting it kubectl delete -f <ingress> should delete the ALB.
I am really wondering if anyone in the community has managed to deploy k3s on EC2 instances and using AWS LB to route traffic to k3s Pods
I wanted to build a dev/test k8s environment (on demand) for development team. I need several independent k8s clusters ( you , you , you ..... everyone will get a k8s cluster ) 😄
Although for production we are using EKS , it would not be viable to launch 10 x EKS clusters and pay hefty $$ to AWS
Any guidance on this would be appretiated
c
You can do both, the former is just more difficult as the k8s aws operator has to have the correct role and tagging on all the resources. The latter is fairly trivial depending on how you are deploying k3s. Are you using terraform or any sort of IaC? The general principal is: • Create an ALB target group containing your ec2 instances for the ports you want (e.g. tcp 80/443) ◦ Your health check should be
http://{instance}/healthz
• Create an ALB with a listener on the same ports (tcp 80/443)
f
@colossal-dentist-5939 thanks for the suggestion , make sense.
@colossal-dentist-5939 a followup question inorder for health check to passs
http://{instance}/healtz
do i need to create a dummy deployment with
/healtz
api --> service --> expose a ingress on
/healtz
?
c
Nope, the nginx ingress contains the
/healthz
endpoint by default
🙌 1
f
You are a ninja @colossal-dentist-5939 thanks for your guidance sir , I am gonna give it a try.
c
@flaky-kilobyte-53977 did you get this working? I suspended work on AWS k8s because my application is VoIP and doesn't get along well with load balancers and NAT
I plan on trying this again soon for non-VoIP applications