Copy edits for typos
This commit is contained in:
@@ -6,7 +6,7 @@ Kubernetes clusters. The add-ons are visible through the API (they can be listed
|
||||
using ```kubectl```), but manipulation of these objects is discouraged because
|
||||
the system will bring them back to the original state, in particular:
|
||||
* if an add-on is stopped, it will be restarted automatically
|
||||
* if an add-on is rolling-updated (for Replication Controlers), the system will stop the new version and
|
||||
* if an add-on is rolling-updated (for Replication Controllers), the system will stop the new version and
|
||||
start the old one again (or perform rolling update to the old version, in the
|
||||
future).
|
||||
|
||||
|
@@ -164,7 +164,7 @@ If you see that, DNS is working correctly.
|
||||
|
||||
## How does it work?
|
||||
SkyDNS depends on etcd for what to serve, but it doesn't really need all of
|
||||
what etcd offers (at least not in the way we use it). For simplicty, we run
|
||||
what etcd offers (at least not in the way we use it). For simplicity, we run
|
||||
etcd and SkyDNS together in a pod, and we do not try to link etcd instances
|
||||
across replicas. A helper container called [kube2sky](kube2sky/) also runs in
|
||||
the pod and acts a bridge between Kubernetes and SkyDNS. It finds the
|
||||
|
@@ -26,7 +26,7 @@ mutation (insertion or removal of a dns entry) before giving up and crashing.
|
||||
|
||||
`--etcd-server`: The etcd server that is being used by skydns.
|
||||
|
||||
`--kube_master_url`: URL of kubernetes master. Reuired if `--kubecfg_file` is not set.
|
||||
`--kube_master_url`: URL of kubernetes master. Required if `--kubecfg_file` is not set.
|
||||
|
||||
`--kubecfg_file`: Path to kubecfg file that contains the master URL and tokens to authenticate with the master.
|
||||
|
||||
|
@@ -14,7 +14,7 @@ containerized applications.
|
||||
|
||||
The [Juju](https://juju.ubuntu.com) system provides provisioning and
|
||||
orchestration across a variety of clouds and bare metal. A juju bundle
|
||||
describes collection of services and how they interelate. `juju
|
||||
describes collection of services and how they interrelate. `juju
|
||||
quickstart` allows you to bootstrap a deployment environment and
|
||||
deploy a bundle.
|
||||
|
||||
@@ -136,7 +136,7 @@ configuration on it's own
|
||||
|
||||
## Installing the kubectl outside of kubernetes master machine
|
||||
|
||||
Download the Kuberentes release from:
|
||||
Download the Kubernetes release from:
|
||||
https://github.com/GoogleCloudPlatform/kubernetes/releases and extract
|
||||
the release, you can then just directly use the cli binary at
|
||||
./kubernetes/platforms/linux/amd64/kubectl
|
||||
|
@@ -1,6 +1,6 @@
|
||||
The
|
||||
[SaltStack pillar](http://docs.saltstack.com/en/latest/topics/pillar/)
|
||||
data is partially statically dervied from the contents of this
|
||||
data is partially statically derived from the contents of this
|
||||
directory. The bulk of the pillars are hard to perceive from browsing
|
||||
this directory, though, because they are written into
|
||||
[cluster-params.sls](cluster-params.sls) at cluster inception.
|
||||
|
Reference in New Issue
Block a user