Skip to content

Commit c8c6623

Browse files
Sebbo92dchaykin
authored andcommitted
Preface and Software Prerequisites
1 parent a219058 commit c8c6623

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
# Preface
22

3-
In a perfect world every written service will work smooth, your test coverage is on top and there are no bugs in your API. But we all know, that we can't achieve this world, sadly. It's not unusual that there's a bug in an API and you have to debug this problem in a production environment. We have faced this problem with our go services in our Kubernetes cluster, and we want to show you how it's possible to remote debug a go service in a Kubernetes cluster.
3+
In a perfect world every written service will work smooth, your test coverage is on top and there are no bugs in the implementation of your API. But we all know, that we can't achieve this world, sadly. It's not unusual that there's a bug and you have to debug this problem in a production environment. We have faced this problem with our go services in our Kubernetes cluster, and we want to show you how it's possible to remote debug a go service in a Kubernetes cluster.
44

55
## Software Prerequisites
66

7-
For this scenario we need some software:
7+
For this case we create a kubernetes cluster running locally on our system. Therefore we need the following software:
88

99
* [Docker Desktop](https://docs.docker.com/get-docker) (used version: 19.03.8)
1010
* [kind (Kubernetes in Docker)](https://kind.sigs.k8s.io) (used version: v0.7.0)
@@ -90,7 +90,7 @@ Have a nice day! 👋
9090
Activate the kube-context for `kubectl` to communicate with the new cluster:
9191

9292
```sh
93-
`kubectl cluster-info --context kind-local-debug-k8s`
93+
kubectl cluster-info --context kind-local-debug-k8s
9494
```
9595

9696
#### Install nginx-ingress
@@ -236,7 +236,7 @@ Let's go through the deployment.
236236
237237
If you did all steps correctly, your pod should be up and running. Check it with `kubectl get pod`. You should see the output with the pod status _Running_ and two additional services _debug-k8s_ and _service-debug_:
238238

239-
```
239+
```sh
240240
NAME READY STATUS RESTARTS AGE
241241
pod/debug-k8s-6d69b65cf-4fl6t 1/1 Running 0 1h
242242

0 commit comments

Comments
 (0)