Skip to content

Commit 14eedcb

Browse files
authored
Update README.md
1 parent 36c6198 commit 14eedcb

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ All-in-all it will look like this picture demonstrates:
3131

3232
### Creating the Kubernetes cluster
3333

34-
###### Start the cluster
34+
#### Start the cluster
3535

3636
Before starting we need to adjust the cluster config file to your environment. Unfortunately, `kind` does not use the environment variables and we have to inject them into the config file with `sed`:
3737

@@ -95,7 +95,7 @@ Activate the kube-context, so that _kubectl_ can communicate with the newly crea
9595

9696
`kubectl cluster-info --context kind-local-debug-k8s`
9797

98-
###### Install nginx-ingress
98+
#### Install nginx-ingress
9999

100100
Source: https://kind.sigs.k8s.io/docs/user/ingress/#ingress-nginx
101101

@@ -108,7 +108,7 @@ Run the following command for it:
108108

109109
`kubectl wait --namespace ingress-nginx --for=condition=ready pod --selector=app.kubernetes.io/component=controller --timeout=120s`
110110

111-
###### Labelling the worker node
111+
#### Labelling the worker node
112112

113113
We would suggest to label a worker node where the pod is going to be deployed: by default, a pod is deployed on one of several worker nodes you might have in the kind cluster. To make it work the docker image must be populated on all worker nodes in the cluster (it takes time). Otherwise, you can get into a situation, in which the pod is started on a node where the docker image is missing. Let's work with a dedicated node and safe the time.
114114

0 commit comments

Comments
 (0)