Add authentik, tidy up recipe-footer

Signed-off-by: David Young <davidy@funkypenguin.co.nz>

docs/kubernetes/deployment/flux/design.md

@@ -63,4 +63,4 @@ Good! I describe how to put this design into action on the [next page](/kubernet
 
 [^1]: ERDs are fancy diagrams for nERDs which [represent cardinality between entities](https://en.wikipedia.org/wiki/Entity%E2%80%93relationship_model#Crow's_foot_notation) scribbled using the foot of a crow 🐓
 
---8<-- "recipe-footer.md"
+{% include 'recipe-footer.md' %}

docs/kubernetes/deployment/flux/install.md

@@ -147,7 +147,7 @@ If you used my template repo, some extra things also happened..
 
 That's best explained on the [next page](/kubernetes/deployment/flux/design/), describing the design we're using...
 
---8<-- "recipe-footer.md"
+{% include 'recipe-footer.md' %}
 
 [^1]: The [template repo](https://github.com/geek-cookbook/template-flux/) also "bootstraps" a simple example re how to [operate flux](/kubernetes/deployment/flux/operate/), by deploying the podinfo helm chart.
 [^2]: TIL that GitHub listens for SSH on `ssh.github.com` on port 443!

docs/kubernetes/deployment/flux/operate.md

@@ -154,6 +154,6 @@ Commit your changes, and once again do the waiting / impatient-reconciling jig.
 
 We did it. The Holy Grail. We deployed an application into the cluster, without touching the cluster. Pinch yourself, and then prove it worked by running `flux get kustomizations`, or `kubectl get helmreleases -n podinfo`.
 
---8<-- "recipe-footer.md"
+{% include 'recipe-footer.md' %}
 
 [^1]: Got suggestions for improvements here? Shout out in the comments below!