Edited to add the default restart policy (always) to clarify value if RestartPolicy is not set.

Generated new .json output for Swagger UI

Added the api/v1/v1.json file to the hack/update-swagger-spec.sh script so it gets updated and built.

Fixes #5057

Reverting last change: Deleted line for building v1 api from the  build file update-swagger-ui.sh and deleted the output file from build (v1.json).
This commit is contained in:
RichieEscarez
2015-05-19 09:34:10 -07:00
parent dcbe815825
commit 0076c181c7
9 changed files with 161 additions and 113 deletions

View File

@@ -25,7 +25,7 @@ More detailed information about the current (and previous) container statuses ca
## RestartPolicy
The RestartPolicy may be `Always`, `OnFailure`, or `Never`. RestartPolicy applies to all containers in the pod. RestartPolicy only refers to restarts of the containers by the Kubelet on the same node. As discussed in the [pods document](pods.md#durability-of-pods-or-lack-thereof), once bound to a node, a pod may never be rebound to another node. This means that some kind of controller is necessary in order for a pod to survive node failure, even if just a single pod at a time is desired.
The possible values for RestartPolicy are `Always`, `OnFailure`, or `Never`. If RestartPolicy is not set, the default value is `Always`. RestartPolicy applies to all containers in the pod. RestartPolicy only refers to restarts of the containers by the Kubelet on the same node. As discussed in the [pods document](pods.md#durability-of-pods-or-lack-thereof), once bound to a node, a pod may never be rebound to another node. This means that some kind of controller is necessary in order for a pod to survive node failure, even if just a single pod at a time is desired.
The only controller we have today is [`ReplicationController`](replication-controller.md). `ReplicationController` is *only* appropriate for pods with `RestartPolicy = Always`. `ReplicationController` should refuse to instantiate any pod that has a different restart policy.