public/geek-cookbook
1
0
Fork 0
mirror of https://github.com/funkypenguin/geek-cookbook/ synced 2025-12-12 17:26:19 +00:00
Code Issues Releases Wiki Activity

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

Browse Source
This commit is contained in:
David Young
2023-01-24 15:32:07 +13:00
parent eafc804e29 fc6712457d
commit 9eec6cd985
3 changed files with 17 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -93,4 +93,4 @@ Impulsively **[click here (NOW quick do it!)][github_sponsor]** to [sponsor me][
[github_sponsor]: https://github.com/sponsors/funkypenguin [github_sponsor]: https://github.com/sponsors/funkypenguin
[discourse]: https://forum.funkypenguin.co.nz/ [discourse]: https://forum.funkypenguin.co.nz/
[contact]: https://www.funkypenguin.co.nz [contact]: https://www.funkypenguin.co.nz
[mastodon]: https://so.fnky.nz/@funkypenguin [mastodon]: https://so.fnky.nz/@funkypenguin

20
docs/kubernetes/loadbalancer/metallb/index.md
View File

@@ -67,17 +67,17 @@ metadata:
### HelmRepository ### HelmRepository
Next, we need to define a HelmRepository (*a repository of helm charts*), to which we'll refer when we create the HelmRelease. We only need to do this once per-repository. In this case, we're using the (*prolific*) [bitnami chart repository](https://github.com/bitnami/charts/tree/master/bitnami), so per the [flux design](/kubernetes/deployment/flux/), I create this example yaml in my flux repo: Next, we need to define a HelmRepository (*a repository of helm charts*), to which we'll refer when we create the HelmRelease. We only need to do this once per-repository. In this case, we're using the (*prolific*) [metallb chart repository](https://github.com/metallb/metallb/tree/main/charts/metallb), so per the [flux design](/kubernetes/deployment/flux/), I create this example yaml in my flux repo:
```yaml title="/bootstrap/helmrepositories/helmrepository-bitnami.yaml" ```yaml title="/bootstrap/helmrepositories/helmrepository-metallb.yaml"
apiVersion: source.toolkit.fluxcd.io/v1beta1 apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmRepository kind: HelmRepository
metadata: metadata:
name: bitnami name: metallb
namespace: flux-system namespace: flux-system
spec: spec:
interval: 15m interval: 15m
url: https://charts.bitnami.com/bitnami url: https://metallb.github.io/metallb
``` ```
### Kustomization ### Kustomization
@@ -113,7 +113,7 @@ spec:
### ConfigMap (for HelmRelease) ### ConfigMap (for HelmRelease)
Now we're into the metallb-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/metallb/values.yaml). Paste the values into a `values.yaml` key as illustrated below, indented 4 spaces (*since they're "encapsulated" within the ConfigMap YAML*). I create this example yaml in my flux repo at ``: Now we're into the metallb-specific YAMLs. First, we create a ConfigMap, containing the entire contents of the helm chart's [values.yaml](https://github.com/metallb/metallb/blob/main/charts/metallb/values.yaml). Paste the values into a `values.yaml` key as illustrated below, indented 4 spaces (*since they're "encapsulated" within the ConfigMap YAML*). I create this example yaml in my flux repo at ``:
```yaml title="/metallb-system/configmap-metallb-helm-chart-value-overrides.yaml" ```yaml title="/metallb-system/configmap-metallb-helm-chart-value-overrides.yaml"
apiVersion: v1 apiVersion: v1
@@ -130,9 +130,7 @@ data:
--8<-- "kubernetes-why-full-values-in-configmap.md" --8<-- "kubernetes-why-full-values-in-configmap.md"
Then work your way through the values you pasted, and change any which are specific to your configuration. I'd recommend changing the following: Then work your way through the values you pasted, and change any which are specific to your configuration.
* `commonAnnotations`: Anticipating the future use of Reloader to bounce applications when their config changes, I add the `configmap.reloader.stakater.com/reload: "metallb-config"` annotation to all deployed objects, which will instruct Reloader to bounce the daemonset if the ConfigMap changes.
### Kustomization for CRs (Config) ### Kustomization for CRs (Config)
@@ -261,10 +259,10 @@ spec:
chart: chart:
spec: spec:
chart: metallb chart: metallb
version: 4.x version: 0.13.7
sourceRef: sourceRef:
kind: HelmRepository kind: HelmRepository
name: bitnami name: metallb
namespace: flux-system namespace: flux-system
interval: 15m interval: 15m
timeout: 5m timeout: 5m

14
docs/kubernetes/ssl-certificates/secret-replicator.md
View File

@@ -82,12 +82,12 @@ data:
# Declare variables to be passed into your templates. # Declare variables to be passed into your templates.
image: image:
repository: kiwigrid/secret-replicator repository: kiwigrid/secret-replicator
tag: 0.2.0 tag: latest #0.2.0 It's 0.1.0 and latest listed in dockerhub. No 0.2.0 anymore
pullPolicy: IfNotPresent pullPolicy: IfNotPresent
## Specify ImagePullSecrets for Pods ## Specify ImagePullSecrets for Pods
## ref: https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod ## ref: https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod
# pullSecrets: myregistrykey # pullSecrets: myregistrykey
# csv list of secrets # csv list of secrets
secretList: "letsencrypt-wildcard-cert" secretList: "letsencrypt-wildcard-cert"
@@ -96,7 +96,7 @@ data:
ignoreNamespaces: "kube-system,kube-public" ignoreNamespaces: "kube-system,kube-public"
# If defined, allow secret-replicator to watch for secrets in _another_ namespace # If defined, allow secret-replicator to watch for secrets in _another_ namespace
secretNamespace: letsencrypt-wildcard-cert" secretNamespace: "letsencrypt-wildcard-cert"
rbac: rbac:
enabled: true enabled: true