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

Add flux bootstrap SSH workaround, bug fixes

Browse Source 
Signed-off-by: David Young <davidy@funkypenguin.co.nz>
This commit is contained in:
David Young
2022-11-10 10:20:38 +13:00
parent 820aee6f88
commit 9272208efe
5 changed files with 18 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/kubernetes/deployment/flux/install.md
View File

@@ -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!

2
docs/kubernetes/persistence/rook-ceph/cluster.md
View File

@@ -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)!
# <upstream values go here>

2
docs/recipes/immich.md
View File

@@ -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..

2
docs/recipes/mastodon.md
View File

@@ -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..

2
docs/recipes/pixelfed.md
View File

@@ -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*)