mirrors
/
kubernetes-the-hard-way
mirror of https://github.com/kelseyhightower/kubernetes-the-hard-way
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

The chapter 'Provisioning Compute Resources' is updated.

pull/443/head
Pick1a1username 2019-02-16 17:11:09 +09:00
parent 1fea217087
commit bda8573e7f
1 changed files with 24 additions and 70 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

94
docs/03-compute-resources.md
View File

@ -137,6 +137,9 @@ Create a virtual machine, instead of Cloud Shell in GCP, that will be used as a
7. Type `client-1`, click Network selection, select the network `kubernetes-nw`, and click Finish. 7. Type `client-1`, click Network selection, select the network `kubernetes-nw`, and click Finish.
## Configure Virtual Machines
### Setup The Hostname and The IP Address of each Virtual Machine ### Setup The Hostname and The IP Address of each Virtual Machine
As described above, the IP address of each virtual machine should be fixed. As described above, the IP address of each virtual machine should be fixed.
@ -206,95 +209,46 @@ $ cat << EOF > new_hosts
EOF EOF
``` ```
### Verification
List the compute instances in your default compute zone:
```
gcloud compute instances list
```
> output
```
NAME ZONE MACHINE_TYPE PREEMPTIBLE INTERNAL_IP EXTERNAL_IP STATUS
controller-0 us-west1-c n1-standard-1 10.240.0.10 XX.XXX.XXX.XXX RUNNING
controller-1 us-west1-c n1-standard-1 10.240.0.11 XX.XXX.X.XX RUNNING
controller-2 us-west1-c n1-standard-1 10.240.0.12 XX.XXX.XXX.XX RUNNING
worker-0 us-west1-c n1-standard-1 10.240.0.20 XXX.XXX.XXX.XX RUNNING
worker-1 us-west1-c n1-standard-1 10.240.0.21 XX.XXX.XX.XXX RUNNING
worker-2 us-west1-c n1-standard-1 10.240.0.22 XXX.XXX.XX.XX RUNNING
```
## Configuring SSH Access ## Configuring SSH Access
SSH will be used to configure the controller and worker instances. When connecting to compute instances for the first time SSH keys will be generated for you and stored in the project or instance metadata as describe in the [connecting to instances](https://cloud.google.com/compute/docs/instances/connecting-to-instance) documentation. SSH will be used to configure the controller and worker instances.
Test SSH access to the `controller-0` compute instances: 1. In the host PC, generate a SSH key.
``` ```
gcloud compute ssh controller-0 $ ssh-keygen
```
If this is your first time connecting to a compute instance SSH keys will be generated for you. Enter a passphrase at the prompt to continue: (...)
```
WARNING: The public SSH key file for gcloud does not exist.
WARNING: The private SSH key file for gcloud does not exist.
WARNING: You do not have an SSH key for gcloud.
WARNING: SSH keygen will be executed to generate a key.
Generating public/private rsa key pair.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
``` ```
At this point the generated SSH keys will be uploaded and stored in your project: 2. Create a text file containing IP addresses of virtual machines.
``` ```
Your identification has been saved in /home/$USER/.ssh/google_compute_engine. $ cat << EOF > target_hosts.txt
Your public key has been saved in /home/$USER/.ssh/google_compute_engine.pub. 10.240.0.10
The key fingerprint is: 10.240.0.11
SHA256:nz1i8jHmgQuGt+WscqP5SeIaSy5wyIJeL71MuV+QruE $USER@$HOSTNAME 10.240.0.12
The key's randomart image is: 10.240.0.13
+---[RSA 2048]----+ 10.240.0.21
| | 10.240.0.22
| | 10.240.0.23
| | 10.240.0.99
| . | EOF
|o. oS |
|=... .o .o o |
|+.+ =+=.+.X o |
|.+ ==O*B.B = . |
| .+.=EB++ o |
+----[SHA256]-----+
Updating project ssh metadata...-Updated [https://www.googleapis.com/compute/v1/projects/$PROJECT_ID].
Updating project ssh metadata...done.
Waiting for SSH key to propagate.
``` ```
After the SSH keys have been updated you'll be logged into the `controller-0` instance: 3. Distribute the key to the virtual machines.
``` ```
Welcome to Ubuntu 18.04 LTS (GNU/Linux 4.15.0-1006-gcp x86_64) $ for target in `cat target_hosts`; do ssh-copy-id -i ~/.ssh/id_rsa-k8s.pub <ID>@$target; done
...
Last login: Sun May 13 14:34:27 2018 from XX.XXX.XXX.XX
``` ```
Type `exit` at the prompt to exit the `controller-0` compute instance: You will be asked to enter password of the user(ID).
4. Verify ...
``` ```
$USER@controller-0:~$ exit $ do ssh -i ~/.ssh/id_rsa-k8s <ID>@$target uname -n; done
```
> output
```
logout
Connection to XX.XXX.XXX.XXX closed
``` ```
Next: [Provisioning a CA and Generating TLS Certificates](04-certificate-authority.md) Next: [Provisioning a CA and Generating TLS Certificates](04-certificate-authority.md)