Summary
Connecting to a fully isolated Kubernetes cluster (private IPs only) is not as straightforward as using a public IP.
This tutorial would cover:
- how to open a SSH tunnel through the Public Gateway bastion to the cluster's control plane
- what to change in the kubeconfig file (point to
127.0.0.1) in order to be able to interact with the cluster
Why is it needed?
I've worked on private clusters in the past, and documentation is usually sparse when it comes to this subject
Want to write this documentation yourself?
Yes
Related PR(s)
No response
(Optional) Scaleway Organization ID
f4f80918-1cda-47ee-ad14-64a0a2b34d55
Email address
No response