public/geek-cookbook
1
0
Fork 0
mirror of https://github.com/funkypenguin/geek-cookbook/ synced 2025-12-13 01:36:23 +00:00
Code Issues Releases Wiki Activity

Try to avoid parsing errors

Browse Source 
Signed-off-by: David Young <davidy@funkypenguin.co.nz>
This commit is contained in:
David Young
2022-02-18 18:00:18 +13:00
parent 6987a67f78
commit cf1645dd2f
4 changed files with 11 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
manuscript/kubernetes/sealed-secrets.md
View File

@@ -107,6 +107,7 @@ Now that the "global" elements of this deployment (*just the HelmRepository in t
### ConfigMap ### 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`: 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)" ??? example "Example ConfigMap (click to expand)"
@@ -466,6 +467,7 @@ Now you're ready to seal some secrets!
### Sealing a secret ### 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*) 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 ```bash
kubeseal --fetch-cert \ kubeseal --fetch-cert \

3
manuscript/recipes/kubernetes/harbor/index.md Normal file
View File

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

1
manuscript/recipes/kubernetes/harbor/istio.md Normal file
View File

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

7
mkdocs.yml
View File

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