all repos — site @ ed57ae28d76a3c8163394876a0155783e1e057b5

source for my site, found at icyphox.sh

Fix broken images
Anirudh Oppiliappan x@icyphox.sh
Sun, 11 Jul 2021 19:04:47 +0530
commit

ed57ae28d76a3c8163394876a0155783e1e057b5

parent

b3aeecc60807848917aa8b8b0c6b0d29a07ecbdb

1 files changed, 2 insertions(+), 2 deletions(-)

jump to
M pages/blog/k8s-at-home.mdpages/blog/k8s-at-home.md

@@ -35,7 +35,7 @@

Since my RPi is behind a CG-NAT, I'm running a Wireguard mesh that looks something like this: -![wireguard mesh](https://x.icyphox.sh/zgELS.png) +![wireguard mesh](https://x.icyphox.sh/X4kgT.png) Wireguard is fairly trivial to set up, and there are tons of guides online, so I'll skip that bit.

@@ -124,7 +124,7 @@ In essence, it makes one of your nodes attract all the traffic,

assigning each `LoadBalancer` service an IP from a configured address pool (not your node IP). In my case: -![jade loadbalancer](https://x.icyphox.sh/HriXv.png) +![jade loadbalancer](https://x.icyphox.sh/zuy96.png) However, this assumes that our load balancer node has a public IP. Well it does, but we're still within our Wireguard network. To actually