[PoC] Kubernetes ingress controller - #162
Draft
patatoid wants to merge 31 commits into
Draft
Conversation
patatoid
force-pushed
the
kubernetes-ingress-controller
branch
2 times, most recently
from
June 4, 2026 05:06
37fac13 to
7644be0
Compare
patatoid
force-pushed
the
kubernetes-ingress-controller
branch
2 times, most recently
from
June 4, 2026 08:22
e73616f to
4814f0c
Compare
patatoid
force-pushed
the
gateway-service-registry
branch
from
June 11, 2026 14:42
3986ef3 to
2e3ab5f
Compare
patatoid
force-pushed
the
kubernetes-ingress-controller
branch
from
August 10, 2026 15:29
e8699c3 to
748df36
Compare
patatoid
force-pushed
the
kubernetes-ingress-controller
branch
from
August 10, 2026 17:17
a37cd89 to
994cd0b
Compare
patatoid
force-pushed
the
kubernetes-ingress-controller
branch
from
August 12, 2026 17:28
994cd0b to
7724d69
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Here is a proof of concept of zero-trust brought to Kubernetes through the implementation of a gateway as an ingress controller and microgateways as sidecars. This enables mTLS interactions between the main ingress and the services with a common authority for the instances forming a cluster as an identity platform to have both authentication, authorization and security provided to secure the infrastructure.
Features
Test
You'll then be able to request the service at
curl http://kagome.local:30080/echopassing through the ingress the connection will go through a mTLS tunnel toward the echo service.