From 4f1e556863b05f68e943336d0b4409f04e36add3 Mon Sep 17 00:00:00 2001 From: Joshua Rogers <690634+joshfrogers@users.noreply.github.com> Date: Sat, 8 Aug 2020 15:31:26 +0100 Subject: [PATCH] Update Portainer.md - invalid link [keepalived](ha-docker-swarm/keepalived/) IP points to https://geek-cookbook.funkypenguin.co.nz/recipes/portainer/ha-docker-swarm/keepalived/ Correct page is https://geek-cookbook.funkypenguin.co.nz/ha-docker-swarm/keepalived/ --- manuscript/recipes/portainer.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/manuscript/recipes/portainer.md b/manuscript/recipes/portainer.md index 09c77f3..496719f 100644 --- a/manuscript/recipes/portainer.md +++ b/manuscript/recipes/portainer.md @@ -12,7 +12,7 @@ This is a "lightweight" recipe, because Portainer is so "lightweight". But it ** 1. [Docker swarm cluster](/ha-docker-swarm/design/) with [persistent shared storage](/ha-docker-swarm/shared-storage-ceph.md) 2. [Traefik](/ha-docker-swarm/traefik) configured per design -3. DNS entry for the hostname you intend to use, pointed to your [keepalived](ha-docker-swarm/keepalived/) IP +3. DNS entry for the hostname you intend to use, pointed to your [keepalived](/ha-docker-swarm/keepalived/) IP ## Preparation @@ -66,4 +66,4 @@ Log into your new instance at https://**YOUR-FQDN**. You'll be prompted to set y ## Chef's Notes 📓 -1. I wanted to use oauth2_proxy to provide an additional layer of security for Portainer, but the proxy seems to break the authentication mechanism, effectively making the stack **so** secure, that it can't be logged into! \ No newline at end of file +1. I wanted to use oauth2_proxy to provide an additional layer of security for Portainer, but the proxy seems to break the authentication mechanism, effectively making the stack **so** secure, that it can't be logged into!