Ingress caching

Python Flask application are serving static files on wsgi through unicorn.

This is not advised as a production serve strategy: having caching at reverse-proxy level can be a good solution.

- [ ] set up ingress to be a dedicated instance for the release/namespace (don't want to mess up cache of different applications on the same cluster
- [ ] configure ingress and configuration genaration to cache static files.

Nice article to start with: https://medium.com/@vdboor/using-nginx-ingress-as-a-static-cache-91bc27be04a1

Start with the linked NGINX Ingress caching article, then inspect the repository's ingress and configuration-generation entry points. The issue is done when each release or namespace has a dedicated ingress and generated configuration caches static files without sharing cache state across applications.

Written by the indexing model from the issue text.