From e4bf1666c61273b2873621087b65a1aaeec6db54 Mon Sep 17 00:00:00 2001 From: Charlie Drage Date: Tue, 18 Apr 2017 10:39:47 -0400 Subject: [PATCH] Update doc with better console output and add note on deployment config Adds note on Deployment Config as well as updates console output for Kubernetes example --- docs/user-guide.md | 33 ++++++++++++++++++--------------- 1 file changed, 18 insertions(+), 15 deletions(-) diff --git a/docs/user-guide.md b/docs/user-guide.md index 7fcb56eb..164ee789 100644 --- a/docs/user-guide.md +++ b/docs/user-guide.md @@ -165,19 +165,21 @@ INFO Successfully created deployment: frontend Your application has been deployed to Kubernetes. You can run 'kubectl get deployment,svc,pods' for details. $ kubectl get deployment,svc,pods -NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE -frontend 1 1 1 1 4m -redis-master 1 1 1 1 4m -redis-slave 1 1 1 1 4m -NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE -frontend 10.0.174.12 80/TCP 4m -kubernetes 10.0.0.1 443/TCP 13d -redis-master 10.0.202.43 6379/TCP 4m -redis-slave 10.0.1.85 6379/TCP 4m -NAME READY STATUS RESTARTS AGE -frontend-2768218532-cs5t5 1/1 Running 0 4m -redis-master-1432129712-63jn8 1/1 Running 0 4m -redis-slave-2504961300-nve7b 1/1 Running 0 4m +NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE +deploy/frontend 1 1 1 1 4m +deploy/redis-master 1 1 1 1 4m +deploy/redis-slave 1 1 1 1 4m + +NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE +svc/frontend 10.0.174.12 80/TCP 4m +svc/kubernetes 10.0.0.1 443/TCP 13d +svc/redis-master 10.0.202.43 6379/TCP 4m +svc/redis-slave 10.0.1.85 6379/TCP 4m + +NAME READY STATUS RESTARTS AGE +po/frontend-2768218532-cs5t5 1/1 Running 0 4m +po/redis-master-1432129712-63jn8 1/1 Running 0 4m +po/redis-slave-2504961300-nve7b 1/1 Running 0 4m ``` Note: - You must have a running Kubernetes cluster with a pre-configured kubectl context. @@ -391,5 +393,6 @@ services: restart: "on-failure" ``` -#### Notes: --- If the Docker Compose file has a volume specified for a service, the Deployment (Kubernetes) or DeploymentConfig (OpenShift) strategy is changed to "Recreate" instead of "RollingUpdate" (default). This is done to avoid multiple instances of a service from accessing a volume at the same time. + +#### Warning about Deployment Config +If the Docker Compose file has a volume specified for a service, the Deployment (Kubernetes) or DeploymentConfig (OpenShift) strategy is changed to "Recreate" instead of "RollingUpdate" (default). This is done to avoid multiple instances of a service from accessing a volume at the same time.