Troubleshooting stuff / docs to write-up

[justingarfield]

If you start seeing any of these error messages when using talosctl kubeconfig or kubectl...
error initializing gzip: rpc error: code = Unavailable desc = error reading from server: unexpected EOF
or
E0825 14:02:45.351703 350 request.go:1116] Unexpected error when reading response body: http2: client connection lost
unexpected error when reading response body. Please retry. Original error: http2: client connection lost
or
E0825 12:45:39.845316 1375 memcache.go:265] couldn't get current server API group list: Get "https://:6443/api?timeout=32s": net/http: TLS handshake timeout
E0825 12:46:11.846729 1375 request.go:1116] Unexpected error when reading response body: net/http: request canceled (Client.Timeout or context cancellation while reading body)
E0825 12:46:11.846789 1375 memcache.go:265] couldn't get current server API group list: unexpected error when reading response body. Please retry. Original error: net/http: request canceled (Client.Timeout or context cancellation while reading body)
--> Check the MTU size of the NIC that your machine / container have their traffic exiting out of <--
I had originally assigned Jumbo Frames (9k bytes) to a NIC for some testing with my NAS, and completely forgot about that when I reassigned it as the NIC that my Development/Tooling Docker containers are using to communicate on my Kubernetes VLAN, and that was enough to cause the above errors (saw the TLS handshake timeouts specifically when attempting to hit the Talos Nodes via my HA Proxy Load Balancer endpoints vs. directly via Control Plane IPs)
In my environment, changing the NIC back to 1500 MTU made my Docker Containers + talosctl + kubectl all happy again 🙂