The reason is simple, the built-in server is single processed and single threaded. Let’s take a minute to understand what the Dockerfiles will need to support the REST API we’ve written.įlask has a built-in web server that is useful during development, however, it is strongly recommended that you not use it for production. Unfortunately, this is outside of the scope of this tutorial.īefore we can create a Docker image we are going to need a Dockerfile. Hashicorp Vault will be the authority of all secrets, and those secrets will be synced to Kubernetes Secrets. While used in this tutorial as an example of handling secrets, you must keep in mind that its purpose is just to transport secrets to pods, for consumption by containers.Ī strongly recommended setup is to use Hashicorp Vault and Kubernetes secrets in concert. Kubernetes Secrets provides simple storage of your sensitive data and files. Secrets can be fetched from a Vault or from Kubernetes Secrets at runtime. All sensitive information, called secrets, should be handled by a secrets vault, such as Hashicorp Vault, or in the case of this tutorial Kubernetes Secrets. As a best practice with Docker and, by extension, Kubernetes, environment specific information should not be stored in a Docker container.Įven more important is not storing credentials in the container or your code. Notice that none of the environmental information is statically stored in config.py. The application will be written as simple CRUD api that will connect with a MySQL database.Ĭonfigurations are stored in a config.py file, which is where the database connections settings will be stored. The following is a basic Flask REST API, which will be used for demonstration purposes. It is also very simple to add uWSGI backend support. NGINX is a highly efficient, event-driven web server that is capable of handling high volumes of traffic. While the container could run the application server alone, a web server provides more control over the traffic hitting our Flask API. NGINX Web ServerĪ web server will handle all incoming requests, and then reverse proxy them to the application server. There are a few servers available, however, this tutorial will cover uWSGI. In order to run the Flask API an application server is required. You will also learn how to create services for your Pods to expose them, as well as how to use secrets for sensitive information. Deployments also provide additional features to control how new image updates are deployed and are handled on failures. The solution provided by this post will use Kubernetes Deployments, which will allow you to scale your application. In this tutorial, you will learn how to build a a RESTful Flask API for Kubernetes, by building a production-ready Docker container.

Run docker on kubernetes secret