amal/ungleich-staticcms
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

[k8s] blog update, +dns

Browse source
This commit is contained in:
Nico Schottelius 2021-06-13 20:39:22 +02:00
commit 97d9ad7886
2 changed files with 178 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

14
content/u/blog/kubernetes-without-ingress/contents.lr
View file

@ -39,6 +39,16 @@ So the ingress basically routes from outside to inside. But, in the
IPv6 world, services are already publicly reachable. It just
depends on your network policy.
### Update 2021-06-13: Ingress vs. Service
As some people pointed out (thanks a lot!), a public service is
**not the same** as an Ingress. Ingress has also the possibility to
route based on layer 7 information like the path, domain name, etc.
However, if all of the traffic from an Ingress points to a single
IPv6 HTTP/HTTPS Service, effectively the IPv6 service will do the
same, with one hop less.
## Services
Let's have a look at how services in IPv6 only clusters look like:
@ -51,8 +61,8 @@ nginx-service ClusterIP 2a0a:e5c0:13:e2::3607 <n
postgres ClusterIP 2a0a:e5c0:13:e2::c9e0 <none> 5432/TCP 19h
...
```
All these services are world reachable, so a theorethical ingress does
actually not do any work. Services are routed to the pods as usual.
All these services are world reachable, depending on your network
policy.
## ServiceTypes