Copy edits for spelling errors and typos
Signed-off-by: Ed Costello <epc@epcostello.com>
This commit is contained in:
@@ -164,7 +164,7 @@ frontend-controller-oh43e 10.2.2.22 php-redis kubernetes/example-guestboo
|
||||
|
||||
## Exposing the app to the outside world
|
||||
|
||||
To makes sure the app is working, you probably want to load it in the browser. For accessing the Guesbook service from the outside world, an Azure endpoint needs to be created like shown on the picture below.
|
||||
To makes sure the app is working, you probably want to load it in the browser. For accessing the Guestbook service from the outside world, an Azure endpoint needs to be created like shown on the picture below.
|
||||
|
||||

|
||||
|
||||
|
@@ -77,7 +77,7 @@ You now need to edit the docker configuration to activate new flags. Again, thi
|
||||
|
||||
This may be in ```/etc/default/docker``` or ```/etc/systemd/service/docker.service``` or it may be elsewhere.
|
||||
|
||||
Regardless, you need to add the following to the docker comamnd line:
|
||||
Regardless, you need to add the following to the docker command line:
|
||||
```sh
|
||||
--bip=${FLANNEL_SUBNET} --mtu=${FLANNEL_MTU}
|
||||
```
|
||||
|
@@ -61,7 +61,7 @@ You now need to edit the docker configuration to activate new flags. Again, thi
|
||||
|
||||
This may be in ```/etc/default/docker``` or ```/etc/systemd/service/docker.service``` or it may be elsewhere.
|
||||
|
||||
Regardless, you need to add the following to the docker comamnd line:
|
||||
Regardless, you need to add the following to the docker command line:
|
||||
```sh
|
||||
--bip=${FLANNEL_SUBNET} --mtu=${FLANNEL_MTU}
|
||||
```
|
||||
|
@@ -14,7 +14,7 @@ Ansible will take care of the rest of the configuration for you - configuring ne
|
||||
|
||||
## Architecture of the cluster
|
||||
|
||||
A Kubernetes cluster reqiures etcd, a master, and n minions, so we will create a cluster with three hosts, for example:
|
||||
A Kubernetes cluster requires etcd, a master, and n minions, so we will create a cluster with three hosts, for example:
|
||||
|
||||
```
|
||||
fed1 (master,etcd) = 192.168.121.205
|
||||
|
@@ -130,7 +130,7 @@ Get info on the pod:
|
||||
|
||||
To test the hello app, we need to locate which minion is hosting
|
||||
the container. Better tooling for using juju to introspect container
|
||||
is in the works but for we can use `juju run` and `juju status` to find
|
||||
is in the works but we can use `juju run` and `juju status` to find
|
||||
our hello app.
|
||||
|
||||
Exit out of our ssh session and run:
|
||||
|
@@ -15,7 +15,7 @@ export LOGGING_DESTINATION=elasticsearch
|
||||
```
|
||||
|
||||
This will instantiate a [Fluentd](http://www.fluentd.org/) instance on each node which will
|
||||
collect all the Dcoker container log files. The collected logs will
|
||||
collect all the Docker container log files. The collected logs will
|
||||
be targeted at an [Elasticsearch](http://www.elasticsearch.org/) instance assumed to be running on the
|
||||
local node and accepting log information on port 9200. This can be accomplished
|
||||
by writing a pod specification and service specification to define an
|
||||
|
@@ -61,7 +61,7 @@ Then the `roles ` variable defines the role of above machine in the same order,
|
||||
|
||||
The `NUM_MINIONS` variable defines the total number of minions.
|
||||
|
||||
The `SERVICE_CLUSTER_IP_RANGE` variable defines the kubernetes service IP range. Please make sure that you do have a valid private ip range defined here, because some IaaS provider may reserve private ips. You can use below three private network range accordin to rfc1918. Besides you'd better not choose the one that conflicts with your own private network range.
|
||||
The `SERVICE_CLUSTER_IP_RANGE` variable defines the kubernetes service IP range. Please make sure that you do have a valid private ip range defined here, because some IaaS provider may reserve private ips. You can use below three private network range according to rfc1918. Besides you'd better not choose the one that conflicts with your own private network range.
|
||||
|
||||
10.0.0.0 - 10.255.255.255 (10/8 prefix)
|
||||
|
||||
@@ -114,7 +114,7 @@ Also you can run kubernetes [guest-example](https://github.com/GoogleCloudPlatfo
|
||||
|
||||
#### IV. Deploy addons
|
||||
|
||||
After the previous parts, you will have a working k8s cluster, this part will teach you how to deploy addones like dns onto the existing cluster.
|
||||
After the previous parts, you will have a working k8s cluster, this part will teach you how to deploy addons like dns onto the existing cluster.
|
||||
|
||||
The configuration of dns is configured in cluster/ubuntu/config-default.sh.
|
||||
|
||||
@@ -150,7 +150,7 @@ After some time, you can use `$ kubectl get pods` to see the dns pod is running
|
||||
|
||||
Generally, what this approach did is quite simple:
|
||||
|
||||
1. Download and copy binaries and configuration files to proper dirctories on every node
|
||||
1. Download and copy binaries and configuration files to proper directories on every node
|
||||
|
||||
2. Configure `etcd` using IPs based on input from user
|
||||
|
||||
|
Reference in New Issue
Block a user