broad-king-333209/30/2022, 7:30 PM
on the control plane nodes
broad-king-333203/26/2023, 10:14 PM
After some seconds later it will end up in errors:
kubectl get ns NAME STATUS AGE default Active 335d kube-system Active 335d kube-public Active 335d kube-node-lease Active 335d
Then the second question is still, if I would loose my kubeconfig, how can I get the config related parameter afterwards without doing a
kubectl get ns Unable to connect to the server: net/http: TLS handshake timeout kubectl get nodes Unable to connect to the server: net/http: TLS handshake timeout
on Ranger Desktop at last resort. Because this also will break my existing services an installation, right?