Skip to content

Commit 0c69a19

Browse files
authored
Merge pull request #30048 from sftim/20211011_tidy_kpng_article
Tidy kpng article
2 parents 873a25a + cde171c commit 0c69a19

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

content/en/blog/_posts/2021-10-18-kpng-specialized-proxiers.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ date: 2021-10-18
55
slug: use-kpng-to-write-specialized-kube-proxiers
66
---
77

8-
Authors: Lars Ekman, Ericsson
8+
**Author**: Lars Ekman (Ericsson)
99

1010
The post will show you how to create a specialized service kube-proxy
1111
style network proxier using Kubernetes Proxy NG
@@ -210,12 +210,12 @@ podip=$(cat /tmp/out | jq -r '.Endpoints[]|select(.Local == true)|select(.IPs.V6
210210
ip6tables -t nat -A PREROUTING -d $xip/128 -j DNAT --to-destination $podip
211211
```
212212

213-
Assuming the json output above is stored in `/tmp/out` ([jq](https://stedolan.github.io/jq/) is an *awesome* program!).
213+
Assuming the JSON output above is stored in `/tmp/out` ([jq](https://stedolan.github.io/jq/) is an *awesome* program!).
214214

215215

216216
As this is an example we make it really simple for ourselves by using
217217
a minor variation of the `kpng-json` backend above. Instead of just
218-
printing, a program is called and the json output is passed as `stdin`
218+
printing, a program is called and the JSON output is passed as `stdin`
219219
to that program. The backend can be tested stand-alone:
220220

221221
```
@@ -233,7 +233,7 @@ While [kpng](https://github.com/kubernetes-sigs/kpng) is in early
233233
stage of development this post wants to show how you may build your
234234
own specialized K8s proxiers in the future. The only thing your
235235
applications need to do is to add the
236-
`service.kubernetes.io/service-proxy-name` label in the service
236+
`service.kubernetes.io/service-proxy-name` label in the Service
237237
manifest.
238238

239239
It is a tedious process to get new features into the `kube-proxy` and

0 commit comments

Comments
 (0)