chore: add MD linter
This commit is contained in:
parent
6338bc36aa
commit
219f85067b
|
@ -0,0 +1,2 @@
|
|||
MD013: false # long lines
|
||||
MD034: false # bare urls
|
|
@ -94,10 +94,10 @@ Your service is now accessible internally, try this in your `bash` container:
|
|||
|
||||
```bash
|
||||
root@bash:/# nslookup simple-service
|
||||
Server: 10.96.0.10
|
||||
Address: 10.96.0.10#53
|
||||
Server: 10.96.0.10
|
||||
Address: 10.96.0.10#53
|
||||
|
||||
Name: simple-service.default.svc.cluster.local
|
||||
Name: simple-service.default.svc.cluster.local
|
||||
Address: 10.96.31.244
|
||||
```
|
||||
|
||||
|
@ -197,10 +197,10 @@ You have seen a lot different `kind` of k8s, let's take a step back and see how
|
|||
## Exercises
|
||||
|
||||
1. Deploy an nginx and expose it internally
|
||||
2. Read [this](https://kubernetes.io/docs/concepts/services-networking/ingress/#simple-fanout) and modify the ingress to have:
|
||||
* `/simple` that goes to the `simple-service`
|
||||
* `/nginx` that goes to your nginx deployment
|
||||
3. Change the `selector` in your `simple-service` look at what is happening
|
||||
1. Read [this](https://kubernetes.io/docs/concepts/services-networking/ingress/#simple-fanout) and modify the ingress to have:
|
||||
* `/simple` that goes to the `simple-service`
|
||||
* `/nginx` that goes to your nginx deployment
|
||||
1. Change the `selector` in your `simple-service` look at what is happening
|
||||
|
||||
## Clean up
|
||||
|
||||
|
|
|
@ -23,4 +23,4 @@ targetCPUUtilizationPercentage: 80
|
|||
* `maxReplicas`: the maximum number of pods running
|
||||
* `minReplicas`: the minimum number of pods running
|
||||
* `scaleTargetRef`: what this HPA targets, here a `Deployment` named `simple-deployment`
|
||||
* `targetCPUUtilizationPercentage`: the percentage of CPU utilization to cross to activate the HPA
|
||||
* `targetCPUUtilizationPercentage`: the percentage of CPU utilization to cross to activate the HPA
|
||||
|
|
|
@ -113,7 +113,7 @@ This is not a hands on on how to install/manage/deploy a k8s cluster.
|
|||
This is neither a hands on to understand how k8s is working internally.
|
||||
If this topic interests you, see [Kubernetes the hard way](https://github.com/kelseyhightower/kubernetes-the-hard-way).
|
||||
|
||||
## What is k8s? What is it used for?
|
||||
## What is k8s? What is it used for
|
||||
|
||||
k8s is an open source system for managing containerized applications across multiple hosts, providing basic mechanisms for deployment, maintenance, and scaling of applications.
|
||||
|
||||
|
|
Loading…
Reference in New Issue