mirror of
https://github.com/funkypenguin/geek-cookbook/
synced 2025-12-14 02:06:32 +00:00
More tidy up and title fixes
Signed-off-by: David Young <davidy@funkypenguin.co.nz>
This commit is contained in:
@@ -1,3 +1,8 @@
|
|||||||
|
---
|
||||||
|
title: Using Authelia to secure services in Docker
|
||||||
|
description: Authelia is an open-source authentication and authorization server providing 2-factor authentication and single sign-on (SSO) for your applications via a web portal.
|
||||||
|
---
|
||||||
|
|
||||||
# Authelia
|
# Authelia
|
||||||
|
|
||||||
[Authelia](https://github.com/authelia/authelia) is an open-source authentication and authorization server providing 2-factor authentication and single sign-on (SSO) for your applications via a web portal. It acts as a companion of reverse proxies like Nginx, Traefik, or HAProxy to let them know whether queries should pass through. Unauthenticated users are redirected to Authelia Sign-in portal instead.
|
[Authelia](https://github.com/authelia/authelia) is an open-source authentication and authorization server providing 2-factor authentication and single sign-on (SSO) for your applications via a web portal. It acts as a companion of reverse proxies like Nginx, Traefik, or HAProxy to let them know whether queries should pass through. Unauthenticated users are redirected to Authelia Sign-in portal instead.
|
||||||
|
|||||||
@@ -1,4 +1,9 @@
|
|||||||
# Design
|
---
|
||||||
|
title: Launch your secure, scalable Docker Swarm
|
||||||
|
description: Using Docker Swarm to build your own container-hosting platform which is highly-available, scalable, portable, secure and automated! 💪
|
||||||
|
---
|
||||||
|
|
||||||
|
# Highly Available Docker Swarm Design
|
||||||
|
|
||||||
In the design described below, our "private cloud" platform is:
|
In the design described below, our "private cloud" platform is:
|
||||||
|
|
||||||
|
|||||||
@@ -1,3 +1,8 @@
|
|||||||
|
---
|
||||||
|
title: Enable Docker Swarm mode
|
||||||
|
description: For truly highly-available services with Docker containers, Docker Swarm is the simplest way to achieve redundancy, such that a single docker host could be turned off, and none of our services will be interrupted.
|
||||||
|
---
|
||||||
|
|
||||||
# Docker Swarm Mode
|
# Docker Swarm Mode
|
||||||
|
|
||||||
For truly highly-available services with Docker containers, we need an orchestration system. Docker Swarm (*as defined at 1.13*) is the simplest way to achieve redundancy, such that a single docker host could be turned off, and none of our services will be interrupted.
|
For truly highly-available services with Docker containers, we need an orchestration system. Docker Swarm (*as defined at 1.13*) is the simplest way to achieve redundancy, such that a single docker host could be turned off, and none of our services will be interrupted.
|
||||||
|
|||||||
@@ -1,4 +1,5 @@
|
|||||||
---
|
---
|
||||||
|
title: Make docker swarm HA with keepalived
|
||||||
description: While having a self-healing, scalable docker swarm is great for availability and scalability, none of that is worth a sausage if nobody can connect to your cluster!
|
description: While having a self-healing, scalable docker swarm is great for availability and scalability, none of that is worth a sausage if nobody can connect to your cluster!
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|||||||
@@ -1,6 +1,6 @@
|
|||||||
---
|
---
|
||||||
title: Using dex for simple, static authentication with traefik-forward-auth
|
title: Secure Traefik using Dex
|
||||||
description: Traefik-forward-auth needs an authentication backend, but if you don't want to use a cloud provider (like Google), you can setup your own simple backend, using Dex
|
description: Traefik forward auth needs an authentication backend, but if you don't want to use a cloud provider, you can setup your own simple backend, using Dex.
|
||||||
---
|
---
|
||||||
# Using Traefik Forward Auth with Dex (Static)
|
# Using Traefik Forward Auth with Dex (Static)
|
||||||
|
|
||||||
|
|||||||
@@ -1,6 +1,6 @@
|
|||||||
---
|
---
|
||||||
title: Log into traefik forward auth with Google authentication
|
title: Secure Traefik with Google Auth
|
||||||
description: Traefik forward auth needs an authentication backend, and one of the simplest to setup, allows users to login with their Google account
|
description: Using Traefik Forward Auth, you can selectively secure your Docker services, using Google as your authentication backend!
|
||||||
---
|
---
|
||||||
# Traefik Forward Auth using Google
|
# Traefik Forward Auth using Google
|
||||||
|
|
||||||
|
|||||||
@@ -1,6 +1,6 @@
|
|||||||
---
|
---
|
||||||
title: Add oauth2 and oidc SSO to Docker with Traefik Forward Auth
|
title: Add SSO to Traefik with Forward Auth
|
||||||
description: Traefik Forward Auth protects services running in Docker Swarm with an additional layer of authentication, and can be integrated into Google, GitHub, even Active Directory auth!
|
description: Traefik Forward Auth protects services running in Docker with an additional layer of authentication, and can be integrated into Keycloak, Google, GitHub, etc.
|
||||||
---
|
---
|
||||||
# Traefik Forward Auth
|
# Traefik Forward Auth
|
||||||
|
|
||||||
|
|||||||
@@ -1,6 +1,6 @@
|
|||||||
---
|
---
|
||||||
title: Authenticate traefik forward auth with Keycloak
|
title: Secure Traefik using Keycloak
|
||||||
description: Traefik forward auth needs an authentication backend, and a perfect match for the self-hosted enthusiast is Keycloak
|
description: Traefik forward auth can selectively secure your Docker services against an authentication backend, and Keycloak is a perfect, self-hosted match.
|
||||||
---
|
---
|
||||||
# Using Traefik Forward Auth with KeyCloak
|
# Using Traefik Forward Auth with KeyCloak
|
||||||
|
|
||||||
|
|||||||
@@ -1,5 +1,7 @@
|
|||||||
# Why Kubernetes?
|
---
|
||||||
|
title: Docker Swarm vs Kubernetes (the winner)
|
||||||
|
description: I cut my cloud-teeth on Docker swarm, but since swarm is all-but-abandoned by Docker/Mirantis, I'm a happy convert to Kubernetes. Here's why...
|
||||||
|
---
|
||||||
My first introduction to Kubernetes was a children's story:
|
My first introduction to Kubernetes was a children's story:
|
||||||
|
|
||||||
<!-- markdownlint-disable MD033 -->
|
<!-- markdownlint-disable MD033 -->
|
||||||
@@ -7,7 +9,7 @@ My first introduction to Kubernetes was a children's story:
|
|||||||
|
|
||||||
## Why Kubernetes?
|
## Why Kubernetes?
|
||||||
|
|
||||||
Why would you want to Kubernetes for your self-hosted recipes, over simple Docker Swarm? Here's my personal take..
|
Why would you want to Kubernetes for your self-hosted recipes, over simple [Docker Swarm](/ha-docker-swarm/)? Here's my personal take..
|
||||||
|
|
||||||
### Docker Swarm is dead
|
### Docker Swarm is dead
|
||||||
|
|
||||||
@@ -39,8 +41,8 @@ So let's get on with learning how to use the tool...
|
|||||||
|
|
||||||
Primarily you need 2 things:
|
Primarily you need 2 things:
|
||||||
|
|
||||||
1. A cluster
|
1. A [cluster](/kubernetes/cluster/)
|
||||||
2. A way to deploy workloads into the cluster
|
2. A way to [deploy workloads](/kubernetes/deployment/) into the cluster
|
||||||
|
|
||||||
Practically, you need some extras too, but you can mix-and-match these.
|
Practically, you need some extras too, but you can mix-and-match these.
|
||||||
|
|
||||||
|
|||||||
@@ -1,3 +1,7 @@
|
|||||||
|
---
|
||||||
|
title: Traefik Ingress Controller's Dashboard
|
||||||
|
description: Unlike competing ingresses (*cough* nginx *cough*), the beautiful Traefik dashboard UI is free for all.
|
||||||
|
---
|
||||||
# Traefik Dashboard
|
# Traefik Dashboard
|
||||||
|
|
||||||
One of the advantages [Traefik](/kubernetes/ingress/traefik/) offers over [Nginx](/kubernetes/ingress/nginx/), is a native dashboard available in the open-source version (*Nginx+, the commercially-supported version, also includes a dashboard*).
|
One of the advantages [Traefik](/kubernetes/ingress/traefik/) offers over [Nginx](/kubernetes/ingress/nginx/), is a native dashboard available in the open-source version (*Nginx+, the commercially-supported version, also includes a dashboard*).
|
||||||
|
|||||||
@@ -1,3 +1,7 @@
|
|||||||
|
---
|
||||||
|
title: Why I use Traefik Ingress Controller
|
||||||
|
description: Among other advantages, I no longer need to replicate SSL certificate secrets for nginx-ingress-controller to consume, once-per-namespace!
|
||||||
|
---
|
||||||
# Traefik Ingress Controller
|
# Traefik Ingress Controller
|
||||||
|
|
||||||
Unlike grumpy ol' man [Nginx](/kubernetes/ingress/ngnix/) :older_man:, Traefik, a microservice-friendly reverse proxy, is relatively fresh in the "cloud-native" space, having been "born" :baby_bottle: [in the same year that Kubernetes was launched](https://techcrunch.com/2020/09/23/five-years-after-creating-traefik-application-proxy-open-source-project-hits-2b-downloads/).
|
Unlike grumpy ol' man [Nginx](/kubernetes/ingress/ngnix/) :older_man:, Traefik, a microservice-friendly reverse proxy, is relatively fresh in the "cloud-native" space, having been "born" :baby_bottle: [in the same year that Kubernetes was launched](https://techcrunch.com/2020/09/23/five-years-after-creating-traefik-application-proxy-open-source-project-hits-2b-downloads/).
|
||||||
|
|||||||
@@ -1,3 +0,0 @@
|
|||||||
# What is this?
|
|
||||||
|
|
||||||
This directory exists to allow me to pull in markdown docs into the LeanPub book structure, which won't show up in the online version.
|
|
||||||
@@ -1,3 +0,0 @@
|
|||||||
# Chef's Favorites (Docker) #
|
|
||||||
|
|
||||||
The following recipes are the chef's current favorites - these are recipes actively in use and updated by @funkypenguin
|
|
||||||
@@ -1,3 +0,0 @@
|
|||||||
# Chef's Favorites (Docker) #
|
|
||||||
|
|
||||||
The following recipes are the chef's current favorites - these are recipes actively in use and updated by @funkypenguin
|
|
||||||
@@ -1,3 +0,0 @@
|
|||||||
# HA Docker Swarm #
|
|
||||||
|
|
||||||
This section introduces the HA Docker Swarm, which will be the basis for all the recipes discussed.
|
|
||||||
@@ -1,3 +0,0 @@
|
|||||||
# Kubernetes #
|
|
||||||
|
|
||||||
This section introduces the Kubernetes design, which will be the basis for all the recipes discussed further.
|
|
||||||
@@ -1,3 +0,0 @@
|
|||||||
# Recipies (Docker) #
|
|
||||||
|
|
||||||
Now follows individual recipes.
|
|
||||||
@@ -1,3 +0,0 @@
|
|||||||
# Recipies (Kubernetes) #
|
|
||||||
|
|
||||||
Now follows individual recipes.
|
|
||||||
@@ -1,3 +0,0 @@
|
|||||||
# Reference #
|
|
||||||
|
|
||||||
Now follows useful elements which are not full recipes.
|
|
||||||
Reference in New Issue
Block a user