This message was deleted.
# k3sa
adamant-kite-43734
08/17/2023, 6:21 PMThis message was deleted.
a
adorable-toddler-38962
08/17/2023, 6:22 PMthis is my current error when trying to access my cluster via the loadbalancer:
Copy code
E0817 12:09:25.128563 20920 memcache.go:265] couldn't get current server API group list: Get "<https://100.102.34.139:6443/api?timeout=32s>": tls: failed to verify certificate: x509: certificate is valid for 10.43.0.1, 100.122.124.30, 100.72.104.73, 127.0.0.1, 192.168.1.175, 192.168.1.24, 192.168.1.25, 192.168.1.26, 2601:281:c500:4f20:182d:d6ff:fe06:943f, 2601:281:d700:f487:dea6:32ff:fe63:1032, 2601:281:d700:f487:dea6:32ff:fe63:1125, 2601:281:d700:f487:dea6:32ff:fe69:4d8, ::1, not 100.102.34.139c
creamy-pencil-82913
08/17/2023, 6:52 PMDon't do that. Kubernetes uses client certificate authentication, if you offload TLS to a load-balancer in front of the control plane that will break.
a
adorable-toddler-38962
08/17/2023, 6:57 PMok what do i do instead?
adorable-toddler-38962
08/17/2023, 7:07 PMoh wait i think i found it, i need to set the
tls-san Copy code
/etc/rancher/k3s/config.yamladorable-toddler-38962
08/17/2023, 7:07 PMc
creamy-pencil-82913
08/17/2023, 7:45 PMOffloading SSL will still break things. Put it in tcp mode.
a
adorable-toddler-38962
08/17/2023, 8:16 PMim not offloading the ssl to the load balancer, k3s is still handling the ssl
136 Views