This section focuses on implementing the kubernetes hello-minikube tutorial adapted to a conventional Django application. The codebase for this tutorial can be cloned from my github repo and we will be working with the part_2-getting-started branch. The kubernetes version for this tutorial is assumed to be 1.9. 1. Requirements OS This tutorial assumes a Mac OS system, but has links on how to run it on a Linux/Ubuntu or Windows OS.

I have been fortunate enough to work in Devops for the past few years. During this time, I have taken an obsession in learning how to manage applications in production, and as a result trying to figure out: How easy is it to push new features to production and to roll back to a previous version predictably and as necessity dictates? How best is it to have a consistent environment where exactly what was tested in development is deployed to production?

Background There are several tutorials that have been written on how to run Django, while using Celery to process asynchronous tasks with AWS SQS as the message broker. However, on implementing the recommended solutions I got unexpected results which include; ghost queues being created by celery and only been limited to run celery in the us-east-1 AWS region. This tutorial focuses on deploying Django 2 with Celery using SQS in any AWS region that supports SQS and has an emphasis on predictability.

The current Django version 2.0 brings about some significant changes; this includes a lack of support for python2. Thus, the focus of this tutorial is on using python3 to build a Django application with celery for asynchronous task processing and Redis as the message broker. The code for this tutorial can by downloaded directly from my github account. Preparation Python3 As Django 2 uses python3, we need to make sure we install it.