mirrors/kubernetes-hands-on
mirrors
/
kubernetes-hands-on
mirror of https://github.com/algolia/kubernetes-hands-on.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

fix: fix markdownlint in CI

This commit is contained in:
antoinegauvain 2019-12-16 14:01:53 +01:00
parent 787c26058c
commit ab899016ae
4 changed files with 7 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
05-pods/README.md
View File

@ -40,7 +40,6 @@ Let's `apply` this manifest to Kubernetes. This will tell Kubernetes to create t
```sh
$ kubectl apply -f 05-pods/01-simple-pod.yml
pod "simple-pod" created
```
@ -52,7 +51,6 @@ Now list all the `pods` running in Kubernetes. `get` is the `ls` of Kubernetes.
```sh
$ kubectl get pod
NAME READY STATUS RESTARTS AGE
simple-pod 1/1 Running 0 4s
```
@ -63,7 +61,6 @@ Let's have a look at the logs of this `pod`:
```sh
$ kubectl logs simple-pod
2018-10-01T09:21:59 INFO This is simple service in version v0.5.0 listening on port 9876 [at line 142]
2018-10-01T09:23:21 INFO /info serving from 172.17.0.4:9876 has been invoked from 172.17.0.1 [at line 101]
2018-10-01T09:23:21 INFO 200 GET /info (172.17.0.1) 1.38ms [at line 1946]
@ -75,7 +72,6 @@ Our first `pod` is now running. Now `describe` it. `describe` is a `get` on ster
```sh
$ kubectl describe pod simple-pod
[a lot of stuff]
IP: 172.17.0.1
@ -89,8 +85,14 @@ Connect to the cluster, and try to `curl` this ip - `172.17.0.4` in the example.
```sh
$ minikube ssh
$ curl 172.17.0.4:9876/info
_ _
_ _ ( ) ( )
___ ___ (_) ___ (_)| |/') _ _ | |_ __
/' _ ` _ `\| |/' _ `\| || , < ( ) ( )| '_`\ /'__`\
| ( ) ( ) || || ( ) || || |\`\ | (_) || |_) )( ___/
(_) (_) (_)(_)(_) (_)(_)(_) (_)`\___/'(_,__/'`\____)
$ curl 172.17.0.4:9876/info
{"host": "172.17.0.4:9876", "version": "0.5.0", "from": "172.17.0.1"}
```

2
06-label-annotation/README.md
View File

@ -30,7 +30,6 @@ Let's list all the pods that are in the `env=production`:
```sh
$ kubectl get pods -l env=production
NAME READY STATUS RESTARTS AGE
nginx 1/1 Running 0 13s
simple-pod 1/1 Running 0 13s
@ -40,7 +39,6 @@ Let's list all the pods that are in the `env=production,tier=frontend`:
```sh
$ kubectl get pods -l env=production,tier=frontend
NAME READY STATUS RESTARTS AGE
nginx 1/1 Running 0 1m
```

2
07-deployment/README.md
View File

@ -70,7 +70,6 @@ Firstly, Kubernetes created a `deployment`. We see a lot of 2s. It is the number
```sh
$ kubectl get pod
NAME READY STATUS RESTARTS AGE
simple-deployment-5f7c895db4-wpv6l 1/1 Running 0 1m
simple-deployment-5f7c895db4-wt9j7 1/1 Running 0 1m
@ -82,7 +81,6 @@ Did Kubernetes created something else for us? Let's have a look
```sh
$ kubectl get all
NAME READY STATUS RESTARTS AGE
pod/simple-deployment-5f7c895db4-wpv6l 1/1 Running 0 4m
pod/simple-deployment-5f7c895db4-wt9j7 1/1 Running 0 4m

1
98-other-topics/README.md
View File

@ -23,7 +23,6 @@ kube-system Active 56d
```sh
$ kubectl get all --namespace=kube-system
[lot of stuff]
```