From a2d4d7fe1a046c7837c4d9f1f4ad0f9720f768d3 Mon Sep 17 00:00:00 2001 From: Nico Schottelius Date: Wed, 9 Jun 2021 18:38:07 +0200 Subject: [PATCH] ++support --- content/u/blog/kubernetes-without-ingress/contents.lr | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/content/u/blog/kubernetes-without-ingress/contents.lr b/content/u/blog/kubernetes-without-ingress/contents.lr index f6ad26a..59078ba 100644 --- a/content/u/blog/kubernetes-without-ingress/contents.lr +++ b/content/u/blog/kubernetes-without-ingress/contents.lr @@ -75,8 +75,9 @@ makes an global IPv6 address be "internal", besides possible network policies. The concept is probably coming from the strict difference of RFC1918 space usually used in k8s clusters and not public IPv4. -This difference does not make a lot of sense in the IPv6 world though -and seeing services as public by default, makes more sense. +This difference does not make a lot of sense in the IPv6 world though. +Seeing **services as public by default**, makes much more sense. +And simplifies your clusters a lot. ### NodePort @@ -172,3 +173,6 @@ to jump through hoops. If you are interesting in continuing the discussion, we are there for you in [the #hacking:ungleich.ch Matrix channel](https://chat.with.ungleich.ch). + +Or if you are interested in an IPv6 only kubernetes cluster, +drop a mail to **support**-at-**ungleich.ch**.