mirror of
https://github.com/funkypenguin/geek-cookbook/
synced 2025-12-13 09:46:23 +00:00
Fix short titles
Signed-off-by: David Young <davidy@funkypenguin.co.nz>
This commit is contained in:
@@ -1,7 +1,8 @@
|
||||
---
|
||||
description: MetalLB - Load-balancing for bare-metal Kubernetes clusters
|
||||
title: MetalLB - Kubernetes Bare-Metal Loadbalancing
|
||||
description: MetalLB - Load-balancing for bare-metal Kubernetes clusters, deployed with Helm via flux
|
||||
---
|
||||
# MetalLB
|
||||
# MetalLB on Kubernetes, via Helm
|
||||
|
||||
[MetalLB](https://metallb.universe.tf/) offers a network [load balancer](/kubernetes/loadbalancer/) implementation which workes on "bare metal" (*as opposed to a cloud provider*).
|
||||
|
||||
@@ -20,7 +21,7 @@ MetalLB does two jobs:
|
||||
|
||||
* [ ] Network firewall/router supporting BGP (*ideal but not required*)
|
||||
|
||||
## Preparation
|
||||
## MetalLB Requirements
|
||||
|
||||
### Allocations
|
||||
|
||||
|
||||
@@ -1,7 +1,8 @@
|
||||
---
|
||||
title: MetalLB BGP config for pfSense - Kubernetes load balancing
|
||||
description: Using MetalLB with pfsense and BGP
|
||||
---
|
||||
# MetalLB with pfSense
|
||||
# MetalLB on Kubernetes with pfSense
|
||||
|
||||
This is an addendum to the MetalLB recipe, explaining how to configure MetalLB to perform BGP peering with a pfSense firewall.
|
||||
|
||||
|
||||
@@ -1,4 +1,7 @@
|
||||
# TopoLVM
|
||||
---
|
||||
title: TopoLVM - Capacity-aware LVM-based storage on Kubernetes
|
||||
---
|
||||
# TopoLVM on Kubernetes
|
||||
|
||||
TopoLVM is **like** [Local Path Provisioner](/kubernetes/persistence/local-path-provisioner/), in that it deals with local volumes specific to each Kubernetes node, but it offers more flexibility, and is more suited for a production deployment.
|
||||
|
||||
|
||||
@@ -1,4 +1,9 @@
|
||||
# Premix via Ansible
|
||||
---
|
||||
title: Deploy Premix Docker Swarm stacks with Ansible
|
||||
description: Here's how we leverage Ansible to deploy Docker Swarm stacks for all Geek Cookbook recipes in Premix!
|
||||
---
|
||||
|
||||
# Deploy Premix Docker Swarm stacks with Ansible
|
||||
|
||||
!!! warning "This section is under construction :hammer:"
|
||||
This section is a serious work-in-progress, and reflects the current development on the [sponsors](https://github.com/sponsors/funkypenguin)'s "premix" repository
|
||||
|
||||
@@ -1,3 +1,7 @@
|
||||
---
|
||||
title: Launch the Autopirate Docker Swarm stack!
|
||||
description: We're done. Launch your stack and enjoy watching the various apps interact with each other!
|
||||
---
|
||||
# Launch Autopirate stack
|
||||
|
||||
!!! warning
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
---
|
||||
title: Backup with restic in Docker Swarm
|
||||
description: Don't be like Cameron. Back up your shizz.
|
||||
---
|
||||
|
||||
|
||||
@@ -1,3 +1,6 @@
|
||||
---
|
||||
title: Docker Swarm Network allocations
|
||||
---
|
||||
# Networks
|
||||
|
||||
In order to avoid IP addressing conflicts as we bring swarm networks up/down, we will statically address each docker overlay network, and record the details below:
|
||||
|
||||
@@ -1,3 +1,6 @@
|
||||
---
|
||||
title: OpenVPN on Docker Swarm
|
||||
---
|
||||
# OpenVPN
|
||||
|
||||
Sometimes you need an OpenVPN tunnel between your docker hosts and some other environment. I needed this to provide connectivity between swarm-deployed services like Home Assistant, and my IOT devices within my home LAN.
|
||||
|
||||
Reference in New Issue
Block a user