tamsin/estradiol.cloud
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix duplicate langage in hugo-on-k8s post

Browse Source
This commit is contained in:
tamsin woo 2024-03-12 20:45:30 -07:00
parent 0357cf8d2d
commit 4abcc7f1d4
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/posts/hugo-on-k8s-nginx/index.md
View File

@ -307,8 +307,8 @@ this part expresses a routing rule: traffic reaching the cluster via
to actually apply this rule, i need an ingress controller. mine is to actually apply this rule, i need an ingress controller. mine is
[ingress-nginx][nginx-ingress]. [ingress-nginx][nginx-ingress].
when i deployed controller in my cluster, it created _some more_ `nginx` `Pod`s when i deployed controller in my cluster, it created _some more_ `nginx` `Pod`s.
in my cluster. these update their configuration dynamically based on the rules 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 also creates a `Service` of
type `LoadBalancer`, which [magically][do-lb] creates a load balancer appliance 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 in my cloud provider. off-screen, i can point DNS to *that* appliance to finish

4
public/posts/hugo-on-k8s-nginx/index.html
View File

@ -314,8 +314,8 @@ and direct it to the <code>Service</code>:</p>
<code>estradiol.cloud</code> should go to my <code>Service</code>, and then to one of its backend <code>Pod</code>s. <code>estradiol.cloud</code> should go to my <code>Service</code>, and then to one of its backend <code>Pod</code>s.
to actually apply this rule, i need an ingress controller. mine is to actually apply this rule, i need an ingress controller. mine is
<a href="https://kubernetes.github.io/ingress-nginx/">ingress-nginx</a>.</p> <a href="https://kubernetes.github.io/ingress-nginx/">ingress-nginx</a>.</p>
<p>when i deployed controller in my cluster, it created <em>some more</em> <code>nginx</code> <code>Pod</code>s <p>when i deployed controller in my cluster, it created <em>some more</em> <code>nginx</code> <code>Pod</code>s.
in my cluster. these update their configuration dynamically based on the rules these update their configuration dynamically based on the rules
in my <code>Ingress</code> resource(s). the controller also also creates a <code>Service</code> of in my <code>Ingress</code> resource(s). the controller also also creates a <code>Service</code> of
type <code>LoadBalancer</code>, which <a href="https://docs.digitalocean.com/products/kubernetes/how-to/add-load-balancers/">magically</a> creates a load balancer appliance type <code>LoadBalancer</code>, which <a href="https://docs.digitalocean.com/products/kubernetes/how-to/add-load-balancers/">magically</a> creates a load balancer appliance
in my cloud provider. off-screen, i can point DNS to <em>that</em> appliance to finish in my cloud provider. off-screen, i can point DNS to <em>that</em> appliance to finish