https://github.com/codebanesr/k8-ingress-kong
Example application using kubernetes / kong / istio-service-mesh with autoinjection. It uses metallb as LoadBalancer
https://github.com/codebanesr/k8-ingress-kong
Last synced: 4 months ago
JSON representation
Example application using kubernetes / kong / istio-service-mesh with autoinjection. It uses metallb as LoadBalancer
- Host: GitHub
- URL: https://github.com/codebanesr/k8-ingress-kong
- Owner: codebanesr
- Created: 2021-10-23T19:25:59.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2021-10-23T19:50:45.000Z (over 4 years ago)
- Last Synced: 2025-09-02T15:06:06.638Z (9 months ago)
- Size: 346 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Important note for this to work
Because Kong will be sitting outside the default namespace, be sure you also label the Kong namespace with istio-injection enabled as well
```kubectl label namespace kong istio-injection=enabled```
## Or else deploy pods in kong namespace as well
# Steps [till i don't find a way to use init containers to apply injection rules]
```
k apply -f k8-ingress-kong
At this phase pods wont have sidecar proxy injected in them, so I am adding the auto injection label
kubectl label namespace mongodb-namespace istio-injection=enabled
Once I delete all pods, when deployment tries to create pods, it ends up injecting the sidecar containers
k -n mongodb-namespace delete pods --all
```
## Result [Traffic flow]
