JacobF

would using the kubectl command cluster info solve this problem? example for a rancher connection: $ kubectl cluster-info Kubernetes control plane is running at https:///k8s/clusters/ CoreDNS is running at https:///k8s/clusters//api/v1/namespaces/kube-system/services/kube-dns:dns/proxy...