From 214027834284bd7230f165c6309fecef996a777e Mon Sep 17 00:00:00 2001
From: Nico Schottelius <nico@nico-notebook.schottelius.org>
Date: Sun, 19 Dec 2021 20:57:08 +0100
Subject: [PATCH] ++django / k8s

---
 .../contents.lr                               | 55 +++++++++++++++++++
 .../contents.lr                               |  2 +-
 2 files changed, 56 insertions(+), 1 deletion(-)
 create mode 100644 content/u/blog/2021-12-19-django-ipv6-kubernetes/contents.lr

diff --git a/content/u/blog/2021-12-19-django-ipv6-kubernetes/contents.lr b/content/u/blog/2021-12-19-django-ipv6-kubernetes/contents.lr
new file mode 100644
index 0000000..e82775d
--- /dev/null
+++ b/content/u/blog/2021-12-19-django-ipv6-kubernetes/contents.lr
@@ -0,0 +1,55 @@
+title: Running Django in Kubernetes IPv6 only
+---
+pub_date: 2021-12-19
+---
+author: ungleich
+---
+twitter_handle: ungleich
+---
+_hidden: no
+---
+_discoverable: yes
+---
+abstract:
+How to run Django in IPv6 only Kubernetes clusters
+---
+body:
+
+## Overview
+
+At ungleich we run quite some amount of
+[Django applications](https://www.djangoproject.com/), some for
+ourselves, some on behalf of our customers. Most of them are currently
+running "natively" on virtual machines. Our objectives are to
+
+* Slowly move our own workload into IPv6 only kubernetes clusters
+* Slowly move our customer applications into IPv6 only kubernetes
+  clusters
+* Offer modern Django Hosting based on Kubernetes
+
+## Status 2021-12-19: initial design phase
+
+At the moment we are looking into what we require for running Django
+applications inside Kubernetes. Some parts are still open, some are
+already set:
+
+* PostgreSQL as the database: this is our standard so far and we don't
+  plan to change it
+
+Undefined at the moment:
+
+* Where/how to generate and serve static files
+  * Same container?
+  * Separate container?
+* Backup sidecare
+  * Restic?
+  * pg_dump?
+  * media / upload files
+* App server
+  * uwsgi
+  * (g)unicorn
+
+## Follow up
+
+If you are interested in Kubernetes or Django, feel free to
+[join us on our open chat](/u/projects/open-chat/).
diff --git a/content/u/blog/2021-12-19-workadventure-ipv6-kubernetes/contents.lr b/content/u/blog/2021-12-19-workadventure-ipv6-kubernetes/contents.lr
index b1b18f0..fcf189c 100644
--- a/content/u/blog/2021-12-19-workadventure-ipv6-kubernetes/contents.lr
+++ b/content/u/blog/2021-12-19-workadventure-ipv6-kubernetes/contents.lr
@@ -22,7 +22,7 @@ and recently even more in IPv6 only Kubernetes clusters. Today we had
 a look at running [WorkAdventure](https://workadventu.re/) in an IPv6
 only kubernetes cluster.
 
-## Status
+## Status: waiting for bugfix
 
 At the moment it looks like as if WorkAdventure cannot run in IPv6
 only Kubernetes clusters. The frontend displays the infamous "Network