diff --git a/content/u/blog/ipv6-only-k8s-no-need-for-loadbalancer/contents.lr b/content/u/blog/ipv6-only-k8s-no-need-for-loadbalancer/contents.lr
index b60c614..58d8d7a 100644
--- a/content/u/blog/ipv6-only-k8s-no-need-for-loadbalancer/contents.lr
+++ b/content/u/blog/ipv6-only-k8s-no-need-for-loadbalancer/contents.lr
@@ -1,4 +1,4 @@
-title: Kubernetes does not need a Loadbalancer
+title: Kubernetes does not need a LoadBalancer nor ingress
 ---
 pub_date: 2021-06-09
 ---
@@ -21,4 +21,13 @@ You might be running services just fine without a loadbalancer
 in Kubernetes. Using public ClusterIP is very easy, especially with
 IPv6 only clusters.
 
-##
+## Background
+
+Typically in loadbalancer
+ingress for public
+
+
+
+## DNS
+
+## Letsencrypt