From 55ee9f092f337b5fe1ca6f2d2df97fe403b55b08 Mon Sep 17 00:00:00 2001 From: David Young Date: Sun, 10 Jul 2022 11:28:53 +1200 Subject: [PATCH] Fix more broken internal links Signed-off-by: David Young --- manuscript/docker-swarm/shared-storage-gluster.md | 2 +- manuscript/kubernetes/ingress/nginx.md | 2 +- manuscript/kubernetes/ingress/traefik/index.md | 2 +- manuscript/kubernetes/loadbalancer/k3s.md | 2 +- manuscript/kubernetes/ssl-certificates/index.md | 2 +- manuscript/kubernetes/ssl-certificates/secret-replicator.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/manuscript/docker-swarm/shared-storage-gluster.md b/manuscript/docker-swarm/shared-storage-gluster.md index 68fa647..546ad80 100644 --- a/manuscript/docker-swarm/shared-storage-gluster.md +++ b/manuscript/docker-swarm/shared-storage-gluster.md @@ -9,7 +9,7 @@ While Docker Swarm is great for keeping containers running (_and restarting thos ### Why GlusterFS? -This GlusterFS recipe was my original design for shared storage, but I [found it to be flawed](shared-storage-ceph/#why-not-glusterfs), and I replaced it with a [design which employs Ceph instead](shared-storage-ceph/#why-ceph). This recipe is an alternate to the Ceph design, if you happen to prefer GlusterFS. +This GlusterFS recipe was my original design for shared storage, but I [found it to be flawed](/docker-swarm/shared-storage-ceph/#why-not-glusterfs), and I replaced it with a [design which employs Ceph instead](/docker-swarm/shared-storage-ceph/#why-ceph). This recipe is an alternate to the Ceph design, if you happen to prefer GlusterFS. ## Ingredients diff --git a/manuscript/kubernetes/ingress/nginx.md b/manuscript/kubernetes/ingress/nginx.md index 0ae2cc6..e2ceaf4 100644 --- a/manuscript/kubernetes/ingress/nginx.md +++ b/manuscript/kubernetes/ingress/nginx.md @@ -5,7 +5,7 @@ description: Nginx Ingress Controller The [Nginx Ingress Controller](https://kubernetes.github.io/ingress-nginx/) is the grandpappy of Ingress Controllers, with releases dating back ot at least 2016. Of course, Nginx itself is a battle-tested rock, [released in 2004](https://en.wikipedia.org/wiki/Nginx) and has been constantly updated / improved ever since. -Having such a pedigree though can make it a little awkward for the unfamiliar to configure Ngnix, whereas something like [Traefik](/kubernetes/ingress/traefik/), being newer-on-the-scene, is more user-friendly, and offers (*among other features*) a free **dashboard**. (*Nginx's dashboard is only available in the commercial Nginx+ package, which is a [monumental PITA](https://www.nginx.com/blog/deploying-nginx-nginx-plus-docker/) to run*) +Having such a pedigree though can make it a little awkward for the unfamiliar to configure Nginx, whereas something like [Traefik](/kubernetes/ingress/traefik/), being newer-on-the-scene, is more user-friendly, and offers (*among other features*) a free **dashboard**. (*Nginx's dashboard is only available in the commercial Nginx+ package, which is a [monumental PITA](https://www.nginx.com/blog/deploying-nginx-nginx-plus-docker/) to run*) Nginx Ingress Controller does make for a nice, simple "default" Ingress controller, if you don't want to do anything fancy. diff --git a/manuscript/kubernetes/ingress/traefik/index.md b/manuscript/kubernetes/ingress/traefik/index.md index 4f8de01..1b37fec 100644 --- a/manuscript/kubernetes/ingress/traefik/index.md +++ b/manuscript/kubernetes/ingress/traefik/index.md @@ -4,7 +4,7 @@ description: Among other advantages, I no longer need to replicate SSL certifica --- # Traefik Ingress Controller -Unlike grumpy ol' man [Nginx](/kubernetes/ingress/ngnix/) :older_man:, Traefik, a microservice-friendly reverse proxy, is relatively fresh in the "cloud-native" space, having been "born" :baby_bottle: [in the same year that Kubernetes was launched](https://techcrunch.com/2020/09/23/five-years-after-creating-traefik-application-proxy-open-source-project-hits-2b-downloads/). +Unlike grumpy ol' man [Nginx](/kubernetes/ingress/nginx/) :older_man:, Traefik, a microservice-friendly reverse proxy, is relatively fresh in the "cloud-native" space, having been "born" :baby_bottle: [in the same year that Kubernetes was launched](https://techcrunch.com/2020/09/23/five-years-after-creating-traefik-application-proxy-open-source-project-hits-2b-downloads/). Traefik natively includes some features which Nginx lacks: diff --git a/manuscript/kubernetes/loadbalancer/k3s.md b/manuscript/kubernetes/loadbalancer/k3s.md index 88ab4d0..413e60d 100644 --- a/manuscript/kubernetes/loadbalancer/k3s.md +++ b/manuscript/kubernetes/loadbalancer/k3s.md @@ -10,7 +10,7 @@ If you want more than one node in your cluster[^1] (*either now or in future*), ## How does it work? -When **not** deployed with `--disable servicelb`, every time you create a service of type `LoadBalancer`, k3s will deploy a daemonset (*a collection of pods which run on every host in the cluster*), listening on that given port on the host. So deploying a LoadBalancer service for nginx on ports 80 and 443, for example, would result in **every** cluster host listening on ports 80 and 443, and sending any incoming traffic to the ngnix service. +When **not** deployed with `--disable servicelb`, every time you create a service of type `LoadBalancer`, k3s will deploy a daemonset (*a collection of pods which run on every host in the cluster*), listening on that given port on the host. So deploying a LoadBalancer service for nginx on ports 80 and 443, for example, would result in **every** cluster host listening on ports 80 and 443, and sending any incoming traffic to the nginx service. ## Well that's great, isn't it? diff --git a/manuscript/kubernetes/ssl-certificates/index.md b/manuscript/kubernetes/ssl-certificates/index.md index eac64bb..69afc34 100644 --- a/manuscript/kubernetes/ssl-certificates/index.md +++ b/manuscript/kubernetes/ssl-certificates/index.md @@ -15,7 +15,7 @@ I've split this section, conceptually, into 3 separate tasks: 1. Setup [Cert Manager](/kubernetes/ssl-certificates/cert-manager/), a controller whose job it is to request / renew certificates 2. Setup "[Issuers](/kubernetes/ssl-certificates/letsencrypt-issuers/)" for LetsEncrypt, which Cert Manager will use to request certificates -3. Setup a [wildcard certificate](/kubernetes/ssl-certificates/wildcard-certificate/) in such a way that it can be used by Ingresses like Traefik or Ngnix +3. Setup a [wildcard certificate](/kubernetes/ssl-certificates/wildcard-certificate/) in such a way that it can be used by Ingresses like Traefik or Nginx --8<-- "recipe-footer.md" diff --git a/manuscript/kubernetes/ssl-certificates/secret-replicator.md b/manuscript/kubernetes/ssl-certificates/secret-replicator.md index 8b086f9..c2124d1 100644 --- a/manuscript/kubernetes/ssl-certificates/secret-replicator.md +++ b/manuscript/kubernetes/ssl-certificates/secret-replicator.md @@ -6,7 +6,7 @@ As explained when creating our [LetsEncrypt Wildcard certificates](/kubernetes/s * [x] A [Kubernetes cluster](/kubernetes/cluster/) * [x] [Flux deployment process](/kubernetes/deployment/flux/) bootstrapped - * [x] [secret-replicator](/kubernetes/secret-replicator/) deployed to request/renew certificates + * [x] [secret-replicator](kubernetes/ssl-certificates/secret-replicator/) deployed to request/renew certificates * [x] [LetsEncrypt Wildcard Certificates](/kubernetes/ssl-certificates/wildcard-certificate/) created in the `letsencrypt-wildcard-cert` namespace Kiwigrid's "[Secret Replicator](https://github.com/kiwigrid/secret-replicator)" is a simple controller which replicates secrets from one namespace to another.[^1]