Merge pull request #1884 from devin-donnelly/release-1.5

Release 1.5
This commit is contained in:
devin-donnelly
2016-12-07 18:06:51 -08:00
committed by GitHub
4 changed files with 5 additions and 2 deletions
+1 -1
View File
@@ -58,4 +58,4 @@ toc:
- title: Running a Single-Instance Stateful Application - title: Running a Single-Instance Stateful Application
path: /docs/tutorials/stateful-application/run-stateful-application/ path: /docs/tutorials/stateful-application/run-stateful-application/
- title: Running a Replicated Stateful Application - title: Running a Replicated Stateful Application
path: /docs/tutorials/stateful-application/run-replicated-stateful-application/ path: /docs/tutorials/stateful-application/run-replicated-stateful-application/
+1 -1
View File
@@ -428,7 +428,7 @@ enterprise directory, kerberos, etc.)
### Creating Certificates ### Creating Certificates
When using client certificate authentication, you can generate certificates When using client certificate authentication, you can generate certificates
using an existing deployment script or manually through `easyrsa` or `openssl.`` using an existing deployment script or manually through `easyrsa` or `openssl.`
#### Using an Existing Deployment Script #### Using an Existing Deployment Script
+2
View File
@@ -43,6 +43,7 @@ killed for this purpose.
Rescheduler doesn't have any user facing configuration (component config) or API. Rescheduler doesn't have any user facing configuration (component config) or API.
It's enabled by default. It can be disabled: It's enabled by default. It can be disabled:
* during cluster setup by setting `ENABLE_RESCHEDULER` flag to `false` * during cluster setup by setting `ENABLE_RESCHEDULER` flag to `false`
* on running cluster by deleting its manifest from master node * on running cluster by deleting its manifest from master node
(default path `/etc/kubernetes/manifests/rescheduler.manifest`) (default path `/etc/kubernetes/manifests/rescheduler.manifest`)
@@ -51,6 +52,7 @@ It's enabled by default. It can be disabled:
To be critical an add-on has to run in `kube-system` namespace (cofigurable via flag) To be critical an add-on has to run in `kube-system` namespace (cofigurable via flag)
and have the following annotations specified: and have the following annotations specified:
* `scheduler.alpha.kubernetes.io/critical-pod` set to empty string * `scheduler.alpha.kubernetes.io/critical-pod` set to empty string
* `scheduler.alpha.kubernetes.io/tolerations` set to `[{"key":"CriticalAddonsOnly", "operator":"Exists"}]` * `scheduler.alpha.kubernetes.io/tolerations` set to `[{"key":"CriticalAddonsOnly", "operator":"Exists"}]`
+1
View File
@@ -23,6 +23,7 @@ each of which has a sequence of steps.
* [StatefulSet Basics](/docs/tutorials/stateful-application/basic-stateful-set/) * [StatefulSet Basics](/docs/tutorials/stateful-application/basic-stateful-set/)
* [Running a Single-Instance Stateful Application](/docs/tutorials/stateful-application/run-stateful-application/) * [Running a Single-Instance Stateful Application](/docs/tutorials/stateful-application/run-stateful-application/)
* [Running a Replicated Stateful Application](/docs/tutorials/stateful-application/run-replicated-stateful-application/) * [Running a Replicated Stateful Application](/docs/tutorials/stateful-application/run-replicated-stateful-application/)
### What's next ### What's next