summaryrefslogtreecommitdiff
path: root/gemfeed/DRAFT-ipv6test-deployment.html
diff options
context:
space:
mode:
Diffstat (limited to 'gemfeed/DRAFT-ipv6test-deployment.html')
-rw-r--r--gemfeed/DRAFT-ipv6test-deployment.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/gemfeed/DRAFT-ipv6test-deployment.html b/gemfeed/DRAFT-ipv6test-deployment.html
index 9bc33ffb..fd4293de 100644
--- a/gemfeed/DRAFT-ipv6test-deployment.html
+++ b/gemfeed/DRAFT-ipv6test-deployment.html
@@ -15,9 +15,9 @@
<br />
<h2 style='display: inline' id='introduction'>Introduction</h2><br />
<br />
-<span>This post covers deploying a simple IPv6/IPv4 connectivity test application to the f3s Kubernetes cluster. The application displays visitors&#39; IP addresses and determines whether they&#39;re connecting via IPv6 or IPv4—useful for testing dual-stack connectivity.</span><br />
+<span>Deploying a simple IPv6/IPv4 connectivity test application to the f3s Kubernetes cluster. It displays visitors&#39; IP addresses and tells them whether they&#39;re connecting via IPv6 or IPv4—useful for testing dual-stack connectivity.</span><br />
<br />
-<span>The interesting technical challenge was preserving the original client IP address through multiple reverse proxies: from the OpenBSD relayd frontends, through Traefik ingress, to the Apache CGI backend.</span><br />
+<span>The interesting bit was preserving the original client IP address through multiple reverse proxies: from the OpenBSD relayd frontends, through Traefik ingress, to the Apache CGI backend.</span><br />
<br />
<a class='textlink' href='./2024-11-17-f3s-kubernetes-with-freebsd-part-1.html'>f3s series</a><br />
<br />