diff --git a/content/posts/hugo-on-k8s-nginx/index.md b/content/posts/hugo-on-k8s-nginx/index.md index 43255ea..bbdab8d 100644 --- a/content/posts/hugo-on-k8s-nginx/index.md +++ b/content/posts/hugo-on-k8s-nginx/index.md @@ -309,7 +309,7 @@ to actually apply this rule, i need an ingress controller. mine is when i deployed controller in my cluster, it created _some more_ `nginx` `Pod`s. these update their configuration dynamically based on the rules -in my `Ingress` resource(s). the controller also also creates a `Service` of +in my `Ingress` resource(s). the controller also creates a `Service` of type `LoadBalancer`, which [magically][do-lb] creates a load balancer appliance in my cloud provider. off-screen, i can point DNS to *that* appliance to finish the setup. diff --git a/public/posts/hugo-on-k8s-nginx/index.html b/public/posts/hugo-on-k8s-nginx/index.html index fc8d6e4..71a7b32 100644 --- a/public/posts/hugo-on-k8s-nginx/index.html +++ b/public/posts/hugo-on-k8s-nginx/index.html @@ -303,7 +303,7 @@ to actually apply this rule, i need an ingress controller. mine is ingress-nginx.

when i deployed controller in my cluster, it created some more nginx Pods. these update their configuration dynamically based on the rules -in my Ingress resource(s). the controller also also creates a Service of +in my Ingress resource(s). the controller also creates a Service of type LoadBalancer, which magically creates a load balancer appliance in my cloud provider. off-screen, i can point DNS to that appliance to finish the setup.