Change Task titles to imperative: Run Apps. (#4025)

This commit is contained in:
Steve Perry 2017-06-08 13:15:43 -07:00 committed by GitHub
parent 962989b443
commit 10cd61bc62
9 changed files with 11 additions and 11 deletions

View File

@ -34,7 +34,7 @@ toc:
- docs/tasks/inject-data-application/distribute-credentials-secure.md
- docs/tasks/inject-data-application/podpreset.md
- title: Running Applications
- title: Run Applications
section:
- docs/tasks/run-application/run-stateless-application-deployment.md
- docs/tasks/run-application/run-single-instance-stateful-application.md

View File

@ -5,7 +5,7 @@ assignees:
- foxish
- janetkuo
- smarterclayton
title: Deleting a Stateful Set
title: Delete a Stateful Set
redirect_from:
- "/docs/tasks/manage-stateful-set/deleting-a-statefulset/"
- "/docs/tasks/manage-stateful-set/deleting-a-statefulset.html"

View File

@ -4,7 +4,7 @@ assignees:
- erictune
- foxish
- smarterclayton
title: Force Deleting StatefulSet Pods
title: Force Delete StatefulSet Pods
redirect:from:
- "/docs/tasks/manage-stateful-set/delete-pods/"
- "/docs/tasks/manage-stateful-set/delete-pods.html"
@ -30,7 +30,7 @@ In normal operation of a StatefulSet, there is **never** a need to force delete
Manual force deletion should be undertaken with caution, as it has the potential to violate the at most one semantics inherent to StatefulSet. StatefulSets may be used to run distributed and clustered applications which have a need for a stable network identity and stable storage. These applications often have configuration which relies on an ensemble of a fixed number of members with fixed identities. Having multiple members with the same identity can be disastrous and may lead to data loss (e.g. split brain scenario in quorum-based systems).
## Deleting Pods
## Delete Pods
You can perform a graceful pod deletion with the following command:

View File

@ -1,7 +1,7 @@
---
assignees:
- janetkuo
title: Performing a Rolling Update Using a Replication Controller
title: Perform Rolling Update Using a Replication Controller
redirect_from:
- "/docs/user-guide/rolling-updates/"
- "/docs/user-guide/rolling-updates.html"

View File

@ -7,7 +7,7 @@ assignees:
- janetkuo
- kow3ns
- smarterclayton
title: Running a Replicated Stateful Application
title: Run a Replicated Stateful Application
redirect_from:
- "/docs/tutorials/stateful-application/run-replicated-stateful-application/"
- "/docs/tutorials/stateful-application/run-replicated-stateful-application.html"
@ -52,7 +52,7 @@ on general patterns for running stateful applications in Kubernetes.
{% capture lessoncontent %}
## Deploying MySQL
## Deploy MySQL
The example MySQL deployment consists of a ConfigMap, two Services,
and a StatefulSet.

View File

@ -1,5 +1,5 @@
---
title: Running a Single-Instance Stateful Application
title: Run a Single-Instance Stateful Application
redirect_from:
- "/docs/tutorials/stateful-application/run-stateful-application/"
- "/docs/tutorials/stateful-application/run-stateful-application.html"

View File

@ -1,5 +1,5 @@
---
title: Running a Stateless Application Using a Deployment
title: Run a Stateless Application Using a Deployment
redirect_from:
- "/docs/user-guide/simple-nginx/"
- "/docs/user-guide/simple-nginx.html"

View File

@ -7,7 +7,7 @@ assignees:
- janetkuo
- kow3ns
- smarterclayton
title: Scaling a StatefulSet
title: Scale a StatefulSet
redirect_from:
- "/docs/tasks/manage-stateful-set/scale-stateful-set/"
- "/docs/tasks/manage-stateful-set/scale-stateful-set.html"

View File

@ -7,7 +7,7 @@ assignees:
- janetkuo
- kow3ns
- smarterclayton
title: Upgrading from PetSets to StatefulSets
title: Upgrade from PetSets to StatefulSets
redirect_from:
- "/docs/tasks/manage-stateful-set/upgrade-pet-set-to-stateful-set/"
- "/docs/tasks/manage-stateful-set/upgrade-pet-set-to-stateful-set.html"