Merge branch 'master' of github.com:geek-cookbook/geek-cookbook

docs/kubernetes/deployment/flux/install.md

@@ -124,7 +124,7 @@ If you used my template repo, some extra things also happened..
 2. Because the `bootstrap` Kustomization includes everything **recursively** under `bootstrap` path in the repo, all of the above were **also** applied to the cluster
 3. I'd pre-prepared a [Namespace](https://github.com/geek-cookbook/template-flux/blob/main/bootstrap/namespaces/namespace-podinfo.yaml), [HelmRepository](https://github.com/geek-cookbook/template-flux/blob/main/bootstrap/helmrepositories/helmrepository-podinfo.yaml), and [Kustomization](https://github.com/geek-cookbook/template-flux/blob/main/bootstrap/kustomizations/kustomization-podinfo.yaml) for "podinfo", a simple example application, so these were applied to the cluster
 4. The kustomization we added for podinfo refers to the `/podinfo` path in the repo, so everything in **this** folder was **also** applied to the cluster
-5. In the `/podinfo` path of the repo is a [HelmRelease](https://github.com/geek-cookbook/template-flux/blob/main/podinfo/helmrelease-podinfo.yaml) (*an object describing how to deploy a helm chart*), and a [ConfigMap](https://github.com/geek-cookbook/template-flux/blob/main/podinfo/configmap-pofinfo-helm-chart-value-overrides-configmap.yaml) (*which ontain the `values.yaml` for the podinfo helm chart*)
+5. In the `/podinfo` path of the repo is a [HelmRelease](https://github.com/geek-cookbook/template-flux/blob/main/podinfo/helmrelease-podinfo.yaml) (*an object describing how to deploy a helm chart*), and a [ConfigMap](https://github.com/geek-cookbook/template-flux/blob/main/podinfo/configmap-podinfo-helm-chart-value-overrides.yaml) (*which ontain the `values.yaml` for the podinfo helm chart*)
 6. Flux recognized the podinfo **HelmRelease**, applied it along with the values in the **ConfigMap**, and consequently we have podinfo deployed from the latest helm chart, into the cluster, and managed by Flux! 💪
 
 ## Wait, but why?

docs/kubernetes/external-dns.md

@@ -70,7 +70,7 @@ Now that the "global" elements of this deployment (*just the HelmRepository in t
 
 ### ConfigMap
 
-Now we're into the external-dns-specific YAMLs. First, we create a ConfigMap, containing the entire contents of the helm chart's [values.yaml](https://github.com/bitnami-labs/external-dns/blob/main/helm/external-dns/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 example yaml in my flux repo at `external-dns/configmap-external-dns-helm-chart-value-overrides.yaml`:
+Now we're into the external-dns-specific YAMLs. First, we create a ConfigMap, containing the entire contents of the helm chart's [values.yaml](https://github.com/bitnami/charts/blob/master/bitnami/external-dns/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 example yaml in my flux repo at `external-dns/configmap-external-dns-helm-chart-value-overrides.yaml`:
 
 ??? example "Example ConfigMap (click to expand)"
     ```yaml
@@ -1001,27 +1001,27 @@ Lastly, having set the scene above, we define the HelmRelease which will actuall
 
 ??? example "Example HelmRelease (click to expand)"
     ```yaml
-    apiVersion: helm.toolkit.fluxcd.io/v2beta1
-    kind: HelmRelease
-    metadata:
-    name: external-dns
-    namespace: external-dns
-    spec:
-    chart:
-        spec:
-        chart: external-dns
-        version: 4.x
-        sourceRef:
-            kind: HelmRepository
-            name: bitnami
-            namespace: flux-system
-    interval: 15m
-    timeout: 5m
-    releaseName: external-dns
-    valuesFrom:
-    - kind: ConfigMap
-        name: external-dns-helm-chart-value-overrides
-        valuesKey: values.yaml # This is the default, but best to be explicit for clarity
+      apiVersion: helm.toolkit.fluxcd.io/v2beta1
+      kind: HelmRelease
+      metadata:
+        name: external-dns
+        namespace: external-dns
+      spec:
+        chart:
+          spec:
+            chart: external-dns
+            version: 4.x
+            sourceRef:
+              kind: HelmRepository
+              name: bitnami
+              namespace: flux-system
+        interval: 15m
+        timeout: 5m
+        releaseName: external-dns
+        valuesFrom:
+        - kind: ConfigMap
+          name: external-dns-helm-chart-value-overrides
+          valuesKey: values.yaml # This is the default, but best to be explicit for clarity
     ```
 
 --8<-- "kubernetes-why-not-config-in-helmrelease.md"