From 9272208efed7d493c8221c2d4e1ccb5a2a1b6794 Mon Sep 17 00:00:00 2001 From: David Young Date: Thu, 10 Nov 2022 10:20:38 +1300 Subject: [PATCH] Add flux bootstrap SSH workaround, bug fixes Signed-off-by: David Young --- docs/kubernetes/deployment/flux/install.md | 14 ++++++++++++++ docs/kubernetes/persistence/rook-ceph/cluster.md | 2 +- docs/recipes/immich.md | 2 +- docs/recipes/mastodon.md | 2 +- docs/recipes/pixelfed.md | 2 +- 5 files changed, 18 insertions(+), 4 deletions(-) diff --git a/docs/kubernetes/deployment/flux/install.md b/docs/kubernetes/deployment/flux/install.md index b28af37..fd6d542 100644 --- a/docs/kubernetes/deployment/flux/install.md +++ b/docs/kubernetes/deployment/flux/install.md @@ -91,6 +91,19 @@ flux bootstrap github \ --path bootstrap ``` +!!! tip "What if SSH is blocked?" + Per [@jmmassou](https://forum.funkypenguin.co.nz/t/install/1541/2?u=funkypenguin), if you're behind a restrictive firewall which may block outgoing SSH, you might see an error like this: + + ``` + SSH key scan for host github.com:443 failed, error: ssh: handshake failed: EOF + ``` + + A clever workaround is to use SSH over port 443 instead (*apparently GitHub is configured to make this work*)[^2], by appending the following to your bootstrap command: + + ``` + --ssh-hostname ssh.github.com:443 + ``` + Once the flux bootstrap is completed without errors, list the pods in the cluster again, with `kubectl get pods -A`. This time, you see something like this: ```bash @@ -134,3 +147,4 @@ That's best explained on the [next page](/kubernetes/deployment/flux/design/), d --8<-- "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! diff --git a/docs/kubernetes/persistence/rook-ceph/cluster.md b/docs/kubernetes/persistence/rook-ceph/cluster.md index 9a2f4d2..cfc7c89 100644 --- a/docs/kubernetes/persistence/rook-ceph/cluster.md +++ b/docs/kubernetes/persistence/rook-ceph/cluster.md @@ -72,7 +72,7 @@ apiVersion: v1 kind: ConfigMap metadata: name: rook-ceph-cluster-helm-chart-value-overrides - namespace: rook-ceph-cluster + namespace: rook-ceph data: values.yaml: |- # (1)! # diff --git a/docs/recipes/immich.md b/docs/recipes/immich.md index 567d295..7d79c4c 100644 --- a/docs/recipes/immich.md +++ b/docs/recipes/immich.md @@ -43,7 +43,7 @@ mkdir -p /var/data/immich/upload mkdir -p /var/data/runtime/immich/database ``` -### Setup Immich enviroment +### Setup Immich environment Create `/var/data/config/immich/immich.env` something like the example below.. diff --git a/docs/recipes/mastodon.md b/docs/recipes/mastodon.md index f65cdb2..3c37bdd 100644 --- a/docs/recipes/mastodon.md +++ b/docs/recipes/mastodon.md @@ -50,7 +50,7 @@ mkdir -p /var/data/runtime/mastodon/postgres !!! question "Why `/var/data/runtime/mastodon` and not just `/var/data/mastodon`?" The data won't be able to be backed up by a regular filesystem backup, because it'll be in use. We still need to store it **somewhere** though, so we use `/var/data/runtime`, which is excluded from automated backups. See [Data Layout](/reference/data_layout/) for details. -### Setup Mastodon enviroment +### Setup Mastodon environment Create `/var/data/config/mastodon/mastodon.env` something like the example below.. diff --git a/docs/recipes/pixelfed.md b/docs/recipes/pixelfed.md index 845ea1c..6f40cb9 100644 --- a/docs/recipes/pixelfed.md +++ b/docs/recipes/pixelfed.md @@ -59,7 +59,7 @@ chown www-data /var/data/pixelfed/ !!! question "Why `/var/data/runtime/pixelfed` and not just `/var/data/pixelfed`?" The data won't be able to be backed up by a regular filesystem backup, because it'll be in use. We still need to store it **somewhere** though, so we use `/var/data/runtime`, which is excluded from automated backups. See [Data Layout](/reference/data_layout/) for details. -### Setup Pixelfed enviroment +### Setup Pixelfed environment Create `/var/data/config/pixelfed/pixelfed.env` something like the example below.. (*see the [official documentation](https://docs.pixelfed.org/technical-documentation/config/) for a list of all possible variables and details*)