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

Some typos corrected from the chapter 1 to 2.

pull/443/head
Pick1a1username 2019-02-20 17:38:00 +09:00
parent 75441d9a8f
commit 95efed6eaa
2 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/01-prerequisites.md
View File

@ -7,7 +7,7 @@ This tutorial leverages KVM. So you need to have a linux machine on which KVM is
The following KVM-related tools will be used frequently:
* [Virtual Machine Manager](https://virt-manager.org/): used to create VMs and Networks.
* [qemu-img](https://qemu.weilnetz.de/doc/qemu-doc.html#disk_005fimages): used to [image files](https://people.gnome.org/~markmc/qcow-image-format-version-1.html).
* [qemu-img](https://qemu.weilnetz.de/doc/qemu-doc.html#disk_005fimages): used to create [image files](https://people.gnome.org/~markmc/qcow-image-format-version-1.html).
In this tutorial, [openSUSE Tumbleweed](https://en.opensuse.org/Portal:Tumbleweed) will be used as host PC, but in most cases there should be no problem caused by specific distributions or libvirt versions.
@ -85,4 +85,4 @@ If you want to setup tmux like above, `ctrl+b` -> `"` twice, then `ctrl+b` -> `a
> Enable `synchronize-panes`: `ctrl+b` then `shift :`. Then type `set synchronize-panes on` at the prompt. To disable synchronization: `set synchronize-panes off`.
>
Next: [Installing the Client Tools](02-client-tools.md)
Next: [Provisioning Compute Resources](02-compute-resources.md)

22
docs/02-compute-resources.md
View File

@ -15,15 +15,15 @@ In this section, Virtual Network will be setup to host the Kubernetes cluster.
1. Open Virtual Machine Manager, and from menu, go to `Edit` -> `Connection Details`.
2. Go to `Virtual Networks` tab, and click the plus(+) button at the left lower side of the window.
3. Type `kubernetes-nw` in the textbox named `Network Name`, and click Forward.
4. Type `10.240.0.0/24` in the textbox named `Network`, type `10.240.0.2` in the textbox named `Start`, type `10.240.0.254` in the textbox named `end`, and click Forward.
3. Type `kubernetes-nw` in the textbox named `Network Name`, and click `Forward`.
4. Type `10.240.0.0/24` in the textbox named `Network`, type `10.240.0.2` in the textbox named `Start`, type `10.240.0.254` in the textbox named `end`, and click `Forward`.
5. You will be asked whether enabling IPv6 or not. Don't check the checkbox, and click `Forward`.
6. Click the radiobutton named `Forwarding to physical network`, type `kubernetes-nw.com` in the textbox named `DNS Domain Name`, and click `Finish`.
## Virtual Machines
The virtual machines in this lab will be provisioned using [Ubuntu Server](https://www.ubuntu.com/server) 16.04. Each virtual machines will be provisioned with a fixed private IP address to simplify the Kubernetes bootstrapping process.
The virtual machines in this lab will be provisioned using [Ubuntu Server](https://www.ubuntu.com/server) [16.04](https://wiki.ubuntu.com/XenialXerus/ReleaseNotes). Each virtual machines will be provisioned with a fixed private IP address to simplify the Kubernetes bootstrapping process.
The following virtual machines will be setup in this chapter:
@ -54,9 +54,9 @@ Create three virtual instances which will host the Kubernetes control plane:
2. Create images for Kubernetes controllers backed by the base image:
```
# qemu-img create -f qcow2 ubuntu-xenial.qcow -b ubuntu-xenial-controller-1.qcow2
# qemu-img create -f qcow2 ubuntu-xenial.qcow -b ubuntu-xenial-controller-2.qcow2
# qemu-img create -f qcow2 ubuntu-xenial.qcow -b ubuntu-xenial-controller-3.qcow2
# qemu-img create -f qcow2 -b ubuntu-xenial.qcow2 ubuntu-xenial-controller-1.qcow2
# qemu-img create -f qcow2 -b ubuntu-xenial.qcow2 ubuntu-xenial-controller-2.qcow2
# qemu-img create -f qcow2 -b ubuntu-xenial.qcow2 ubuntu-xenial-controller-3.qcow2
```
(Using each image created above, repeat from 3. to 7..)
@ -80,9 +80,9 @@ Create three virtual machines which will host the Kubernetes worker nodes:
2. Create images for Kubernetes controllers backed by the base image:
```
# qemu-img create -f qcow2 ubuntu-xenial.qcow -b ubuntu-xenial-worker-1.qcow2
# qemu-img create -f qcow2 ubuntu-xenial.qcow -b ubuntu-xenial-worker-2.qcow2
# qemu-img create -f qcow2 ubuntu-xenial.qcow -b ubuntu-xenial-worker-3.qcow2
# qemu-img create -f qcow2 -b ubuntu-xenial.qcow2 ubuntu-xenial-worker-1.qcow2
# qemu-img create -f qcow2 -b ubuntu-xenial.qcow2 ubuntu-xenial-worker-2.qcow2
# qemu-img create -f qcow2 -b ubuntu-xenial.qcow2 ubuntu-xenial-worker-3.qcow2
```
(Using each image created above, repeat from 3. to 7..)
@ -101,7 +101,7 @@ Create three virtual machines which will host the Kubernetes worker nodes:
2. Create images for Kubernetes controllers backed by the base image:
```
# qemu-img create -f qcow2 ubuntu-xenial.qcow -b ubuntu-xenial-lb-1.qcow2
# qemu-img create -f qcow2 -b ubuntu-xenial.qcow2 ubuntu-xenial-lb-1.qcow2
```
3. Open Virtual Machine Manager, and click the icon named `Create a new virtual machine`.
@ -120,7 +120,7 @@ Instead of Cloud Shell in GCP, create a virtual machine that will be used as a c
2. Create images for Kubernetes controllers backed by the base image:
```
# qemu-img create -f qcow2 ubuntu-xenial.qcow -b ubuntu-xenial-client-1.qcow2
# qemu-img create -f qcow2 -b ubuntu-xenial.qcow2 ubuntu-xenial-client-1.qcow2
```
3. Open Virtual Machine Manager, and click the icon named `Create a new virtual machine`.
4. Check the radiobutton named `Importing existing disk image`, and click `Forward`.