whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix leading spaces in kubectl commands

Browse Source 
This is causing bash/zsh shells to not to record the executed command in the
history. See this link for details: https://unix.stackexchange.com/questions/115917/why-is-bash-not-storing-commands-that-start-with-spaces

Signed-off-by: Ahmet Alp Balkan <ahmetb@google.com>
This commit is contained in:
Ahmet Alp Balkan
2017-08-05 21:22:56 -07:00
committed by Andrew Chen
parent 0c6bca5b7f
commit a86d9355b0
20 changed files with 93 additions and 93 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tasks/run-application/run-single-instance-stateful-application.md
+5 -5
View File
@@ -85,11 +85,11 @@ for a secure solution.
1. Deploy the contents of the YAML file:
kubectl create -f https://k8s.io/docs/tasks/run-application/mysql-deployment.yaml
kubectl create -f https://k8s.io/docs/tasks/run-application/mysql-deployment.yaml
1. Display information about the Deployment:
kubectl describe deployment mysql
kubectl describe deployment mysql
Name: mysql
Namespace: default
@@ -108,14 +108,14 @@ for a secure solution.
1. List the pods created by the Deployment:
kubectl get pods -l app=mysql
kubectl get pods -l app=mysql
NAME READY STATUS RESTARTS AGE
mysql-63082529-2z3ki 1/1 Running 0 3m
1. Inspect the Persistent Volume:
kubectl describe pv mysql-pv
kubectl describe pv mysql-pv
Name: mysql-pv
Labels: <none>
@@ -135,7 +135,7 @@ for a secure solution.
1. Inspect the PersistentVolumeClaim:
kubectl describe pvc mysql-pv-claim
kubectl describe pvc mysql-pv-claim
Name: mysql-pv-claim
Namespace: default
docs/tasks/run-application/run-stateless-application-deployment.md
+8 -8
View File
@@ -38,11 +38,11 @@ a Deployment that runs the nginx:1.7.9 Docker image:
1. Create a Deployment based on the YAML file:
kubectl create -f https://k8s.io/docs/tasks/run-application/deployment.yaml
kubectl create -f https://k8s.io/docs/tasks/run-application/deployment.yaml
1. Display information about the Deployment:
kubectl describe deployment nginx-deployment
kubectl describe deployment nginx-deployment
user@computer:~/kubernetes.github.io$ kubectl describe deployment nginx-deployment
Name: nginx-deployment
@@ -64,7 +64,7 @@ a Deployment that runs the nginx:1.7.9 Docker image:
1. List the pods created by the deployment:
kubectl get pods -l app=nginx
kubectl get pods -l app=nginx
NAME READY STATUS RESTARTS AGE
nginx-deployment-1771418926-7o5ns 1/1 Running 0 16h
@@ -72,7 +72,7 @@ a Deployment that runs the nginx:1.7.9 Docker image:
1. Display information about a pod:
kubectl describe pod <pod-name>
kubectl describe pod <pod-name>
where `<pod-name>` is the name of one of your pods.
@@ -85,11 +85,11 @@ specifies that the deployment should be updated to use nginx 1.8.
1. Apply the new YAML file:
kubectl apply -f https://k8s.io/docs/tutorials/stateless-application/deployment-update.yaml
kubectl apply -f https://k8s.io/docs/tutorials/stateless-application/deployment-update.yaml
1. Watch the deployment create pods with new names and delete the old pods:
kubectl get pods -l app=nginx
kubectl get pods -l app=nginx
## Scaling the application by increasing the replica count
@@ -101,11 +101,11 @@ should have four pods:
1. Apply the new YAML file:
kubectl apply -f https://k8s.io/docs/tutorials/stateless-application/deployment-scale.yaml
kubectl apply -f https://k8s.io/docs/tutorials/stateless-application/deployment-scale.yaml
1. Verify that the Deployment has four pods:
kubectl get pods -l app=nginx
kubectl get pods -l app=nginx
The output is similar to this: