Merge branch 'master' into release-1.8

This commit is contained in:
steveperry-53
2017-08-25 10:30:26 -07:00
34 changed files with 311 additions and 118 deletions
+6 -6
View File
@@ -77,9 +77,9 @@ Cluster DNS is a DNS server, in addition to the other DNS server(s) in your envi
Containers started by Kubernetes automatically include this DNS server in their DNS searches.
#### User interface
#### Web UI (Dashboard)
The kube-ui provides a read-only overview of the cluster state. For more information, see [Using an HTTP Proxy to Access the Kubernetes API](/docs/tasks/access-kubernetes-api/http-proxy-access-api/)
[Dashboard](/docs/tasks/access-application-cluster/web-ui-dashboard/) is a general purpose, web-based UI for Kubernetes clusters. It allows users to manage and troubleshoot applications running in the cluster, as well as the cluster itself.
#### Container Resource Monitoring
@@ -115,20 +115,20 @@ network rules on the host and performing connection forwarding.
### docker
docker is used for running containers.
`docker` is used for running containers.
### rkt
rkt is supported experimentally for running containers as an alternative to docker.
`rkt` is supported experimentally for running containers as an alternative to docker.
### supervisord
supervisord is a lightweight process monitor and control system that can be used to keep kubelet and docker
`supervisord` is a lightweight process monitor and control system that can be used to keep kubelet and docker
running.
### fluentd
fluentd is a daemon which helps provide [cluster-level logging](#cluster-level-logging).
`fluentd` is a daemon which helps provide [cluster-level logging](#cluster-level-logging).
{% endcapture %}
{% include templates/concept.md %}
@@ -123,7 +123,7 @@ Some possible patterns for communicating with pods in a DaemonSet are:
- **Push**: Pods in the DaemonSet are configured to send updates to another service, such
as a stats database. They do not have clients.
- **NodeIP and Known Port**: Pods in the DaemonSet can use a `hostPort`, so that the pods are reachable via the node IPs. Clients know the list of nodes ips somehow, and know the port by convention.
- **NodeIP and Known Port**: Pods in the DaemonSet can use a `hostPort`, so that the pods are reachable via the node IPs. Clients know the list of node IPs somehow, and know the port by convention.
- **DNS**: Create a [headless service](/docs/user-guide/services/#headless-services) with the same pod selector,
and then discover DaemonSets using the `endpoints` resource or retrieve multiple A records from
DNS.
@@ -15,8 +15,7 @@ PetSets feature from 1.4. Users of PetSets are referred to the 1.5
[Upgrade Guide](/docs/tasks/manage-stateful-set/upgrade-pet-set-to-stateful-set/)
for further information on how to upgrade existing PetSets to StatefulSets.**
A StatefulSet is a Controller that provides a unique identity to its Pods. It provides
guarantees about the ordering of deployment and scaling.
{% include templates/glossary/snippet.md term="statefulset" length="long" %}
{% endcapture %}
{% capture body %}
@@ -40,6 +39,7 @@ provides a set of stateless replicas. Controllers such as
[ReplicaSet](/docs/concepts/workloads/controllers/replicaset/) may be better suited to your stateless needs.
## Limitations
* StatefulSet is a beta resource, not available in any Kubernetes release prior to 1.5.
* As with all alpha/beta resources, you can disable StatefulSet through the `--runtime-config` option passed to the apiserver.
* The storage for a given Pod must either be provisioned by a [PersistentVolume Provisioner](http://releases.k8s.io/{{page.githubbranch}}/examples/persistent-volume-provisioning/README.md) based on the requested `storage class`, or pre-provisioned by an admin.