k3s
k3s copied to clipboard
Need to enable Ping so Rancher HA healthcheck passes
Describe the bug Tried to create Rancher HA machine using k3s and it won't pass healthcheck
To Reproduce
- Create 3 ubuntu machines on AWS
- Setup Amazon load balancer for those machine
- Ssh on first machine and install k3s & start server
- Add other two machine as k3s agents
- Add Helm
- Install Tiller
- Install Ingress & Cert
- Install Rancher using ha/Helm-rancher directions
Expected behavior Rancher HA running on k3s machine.
Additional context
Need to enable Ping for k3s

Since the default ping setup for AWS ELBs is http://instance:80/index.html it seems like it might be a port configuration issue with the Rancher install. Are you able to verify that Rancher is accessible from port 80 on the instances? If it is redirecting to 443 that may be causing issues with ping also.
I have a feeling this is not something we should change in k3s (creating a built-in web server running on port 80 is likely to be problematic since traefik install by default creates a loadbalancer for that port). I think it may be better to select another ping method (https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-healthchecks.html), or ensure there is a working service on port 80 running in k3s.
I think we need to address this docs issue as well: https://github.com/rancher/docs/issues/1241
Closing due to age