ungleich-staticcms/content/u/blog/2021-12-19-django-ipv6-kubernetes/contents.lr
2021-12-20 11:27:49 +01:00

64 lines
1.6 KiB
Markdown

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
### One container providing port 80
* The outside world does not need to know what is running inside
* Thus the django container should:
* Expose port 80
* Serve staticfiles on its own
* One can use *any* of the wsgi/asgi servers
* Will provide example for some of them
## Follow up
If you are interested in Kubernetes or Django, feel free to
[join us on our open chat](/u/projects/open-chat/).