Try to avoid parsing errors

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

manuscript/kubernetes/sealed-secrets.md

@@ -107,6 +107,7 @@ Now that the "global" elements of this deployment (*just the HelmRepository in t
 
 ### ConfigMap
 
+{% raw %}
 Now we're into the sealed-secrets-specific YAMLs. First, we create a ConfigMap, containing the entire contents of the helm chart's [values.yaml](https://github.com/bitnami-labs/sealed-secrets/blob/main/helm/sealed-secrets/values.yaml). Paste the values into a `values.yaml` key as illustrated below, indented 4 tabs (*since they're "encapsulated" within the ConfigMap YAML*). I create this in my flux repo at `sealed-secrets/configmap-sealed-secrets-helm-chart-value-overrides.yaml`:
 
 ??? example "Example ConfigMap (click to expand)"
@@ -466,6 +467,7 @@ Now you're ready to seal some secrets!
 ### Sealing a secret
 
 To generate sealed secrets, we need the public key that the controller has generated. On a host with a valid `KUBECONFIG` env var, pointing to a kubeconfig file with cluster-admin privileges, run the following to retrieve the public key for the sealed secrets (*this is the public key, it doesn't need to be specifically protected*)
+{% endraw %}
 
 ```bash
 kubeseal --fetch-cert \

manuscript/recipes/kubernetes/harbor/index.md

@@ -0,0 +1,3 @@
+# Harbor
+
+harbor

manuscript/recipes/kubernetes/harbor/istio.md

@@ -0,0 +1 @@
+# Istio with Harbor

mkdocs.yml

@@ -207,8 +207,11 @@ nav:
       #   - Dashboard: kubernetes/wip.md
       #   - Kured: kubernetes/wip.md
       #   - KeyCloak: kubernetes/wip.md
-      # - Recipes:
-      #   - GitHub Actions Runners: kubernetes/wip.md
+      - Recipes:
+        - Harbor:
+          - recipes/kubernetes/harbor/index.md
+          Istio: recipes/kubernetes/harbor/istio.md
+        # - GitHub Actions Runners: kubernetes/wip.md
       #   - Cilium: kubernetes/wip.md
       #   - Concourse: kubernetes/wip.md
       #   - Flagger: kubernetes/wip.md