@@ -5,7 +5,7 @@ date: 2021-10-18
5
5
slug : use-kpng-to-write-specialized-kube-proxiers
6
6
---
7
7
8
- Authors : Lars Ekman, Ericsson
8
+ ** Author ** : Lars Ekman ( Ericsson)
9
9
10
10
The post will show you how to create a specialized service kube-proxy
11
11
style network proxier using Kubernetes Proxy NG
@@ -210,12 +210,12 @@ podip=$(cat /tmp/out | jq -r '.Endpoints[]|select(.Local == true)|select(.IPs.V6
210
210
ip6tables -t nat -A PREROUTING -d $xip/128 -j DNAT --to-destination $podip
211
211
```
212
212
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!).
214
214
215
215
216
216
As this is an example we make it really simple for ourselves by using
217
217
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 `
219
219
to that program. The backend can be tested stand-alone:
220
220
221
221
```
@@ -233,7 +233,7 @@ While [kpng](https://github.com/kubernetes-sigs/kpng) is in early
233
233
stage of development this post wants to show how you may build your
234
234
own specialized K8s proxiers in the future. The only thing your
235
235
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
237
237
manifest.
238
238
239
239
It is a tedious process to get new features into the ` kube-proxy ` and
0 commit comments