You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/kubernetes/how-to/connect-private-cluster.mdx
+33-37Lines changed: 33 additions & 37 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,71 +29,67 @@ To connect to the fully isolated Kubernetes Kapsule control plane, you can open
29
29
30
30
### Finding your cluster's URL
31
31
32
-
In the Scaleway console, go to the [Kubernetes product section](https://console.scaleway.com/kubernetes), then click your cluster's name.
33
-
34
-
Scroll down to the **Network** section, and click on the **URL** value. The URL is copied to your clipboard.
32
+
1. Click **Kubernetes** in the **Containers** section of the [Scaleway console](https://console.scaleway.com) side menu. The Kubernetes dashboard displays.
33
+
2. From the drop-down menu, select the geographical region you want to manage.
34
+
3. Click on the name of the cluster you want to connect to. The cluster overview page displays.
35
+
4. Scroll down to the **Network** section, then click the **URL** value. The URL is copied to your clipboard.
35
36
36
37
### Opening the SSH tunnel
37
38
38
39
Open a terminal on your computer, then run the following command:
-`-N` tells `ssh` not to run a remote command, which is the case here since we only want to port-forward;
58
-
-`-L` sets up port-forwarding from a local port (here, port `6443`) and a given host and port on the remote side;
59
-
-`-p` indicates the remote SSH port.
52
+
<Messagetype="note">
53
+
The command contains several `ssh` flags:
60
54
61
-
</Message>
55
+
-`-f` runs the command in the background;
56
+
-`-N` tells `ssh` not to run a remote command, which is the case here since we only want to port-forward;
57
+
-`-L` sets up port-forwarding from a local port (here, port `6443`) and a given host and port on the remote side;
58
+
-`-p` indicates the remote SSH port.
59
+
</Message>
62
60
63
61
A tunnel to the Kubernetes Kapsule control plane is opened: all local traffic to port `6443` will now be redirected to the control plane through the Public Gateway's SSH bastion.
64
62
65
63
## Accessing the cluster
66
64
67
-
### Editing the `/etc/hosts` file
65
+
### Editing the /etc/hosts file
68
66
69
67
The downloaded `kubeconfig` file points to the control plane's URL, which is currently unreachable due to its lack of public IP. However, you can redirect traffic to your local port-forwarded port by editing your `/etc/hosts` file.
70
68
71
69
Open the `/etc/hosts` file on your computer using a text editor, and add the following line:
72
70
73
-
```
74
-
127.0.0.1 <CLUSTER_URL_WITHOUT_HTTPS>
75
-
```
71
+
```
72
+
127.0.0.1 <CLUSTER_URL_WITHOUT_HTTPS>
73
+
```
76
74
77
-
Using the same values as the previous example, the line would be:
75
+
Using the same values as the previous example, the line would be:
0 commit comments