-
Notifications
You must be signed in to change notification settings - Fork 68
/
_ssh-cluster-master-node.html.md.erb
50 lines (37 loc) · 1.52 KB
/
_ssh-cluster-master-node.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
1. Log in to the BOSH Director. For instructions, see [Log in to the BOSH Director VM](diagnostic-tools.html#alias).
1. To identify your Kubernetes cluster deployment name, run the following command:
```
bosh -e ENVIRONMENT deployments
```
Where `ENVIRONMENT` is your BOSH environment alias.
<br>
For example:
```console
$ bosh -e tkgi deployments
```
Kubernetes cluster deployment names begin with `service-instance` and include
a BOSH-generated identifier.
1. To identify your Kubernetes cluster VM name, run the following command:
```
bosh -e ENVIRONMENT -d DEPLOYMENT vms
```
Where:
* `ENVIRONMENT` is the BOSH environment alias.
* `DEPLOYMENT` is your Kubernetes cluster deployment name.
For example:
```console
$ bosh -e tkgi -d service-instance_ae681cd1-7ff4-4661-b12c-49a5b543f16f vms
```
Each Kubernetes cluster VM name begins with `master` or `worker` and includes a BOSH-generated identifier.
1. To SSH into your Kubernetes cluster VM, run the following command:
```
bosh -e ENVIRONMENT -d DEPLOYMENT ssh CLUSTER-VM
```
Where:
* `ENVIRONMENT` is the BOSH environment alias.
* `DEPLOYMENT` is your Kubernetes cluster deployment name.
* `CLUSTER-VM` is your Kubernetes cluster VM name, either `master/VM-ID` or `worker/VM-ID`.
For example:
```console
$ bosh -e tkgi -d service-instance_ae681cd1-7ff4-4661-b12c-49a5b543f16f ssh master/000a1111-222b-3333-4cc5-de66f7a8899b
```