I currently observed with ClashX that if a website both resolves in IPv4 and IPv6, the IPv4 address will have a precedence over the IPv6 one. But in some environments, only IPv6 address is reachable, and access from IPv4 is forbidden, so providing an option for IPv6 precedence is reasonable. Would you please offer this feature?

My routing config is as fo

Right now we emit a message like

T: Error: Unable to find cluster information
T: No current-context set. Please use the --context option to 
T: explicitly set the context.

This is all fine, but some higher-level explanation would be helpful as well, probably linking to documentation:

T: Telepresence uses kubectl/oc to access your Kubernetes/OpenShift
T: cluster. Ple

I think it would be good to describe/list the capture technologies Wireguard is using for each platform. e.g. Windows it using wintun.net driver, Linux it is using /dev/tun etc.

Likely an advanced topic.