maas-ingress and maas-ingress-errors pods with non-root user
Run the maas-ingress and maas-ingress-vip containers with the 'www-data' (33) user Run the maas-ingress-errors container with the error-page image , from  which already runs as nobody user.  Dockerfile.404-server-with-metrics  https://github.com/kubernetes/ingress-gce Change-Id: Idf3791a958017d512bb3f5015b59452e2831b1b3
|4 months ago|
|charts/maas||2 weeks ago|
|images||7 months ago|
|tools||4 months ago|
|.gitignore||1 year ago|
|.gitreview||5 months ago|
|.zuul.yaml||3 months ago|
|LICENSE||1 year ago|
|Makefile||10 months ago|
|README.md||1 year ago|
This repository holds artifacts supporting the deployment of Canonical MaaS in a Kubernetes cluster.
The MaaS install is made up of two required imags and one optional image. The Dockerfiles in this repo can be used to build all three. These images are intended to be deployed via a Kubernetes Helm chart.
The regiond Dockerfile builds a systemD-based Docker image to run the MaaS Region API server and metadata server.
The rackd Dockerfile builds a systemD-based Docker image to run the MaaS Rack controller and dependent services (DHCPd, TFTPd, etc…). This image needs to be run in privileged host networking mode to function.
The cache image Dockerfile simply provides a point-in-time mirror of the maas.io image repository so that if you are deploying MaaS somewhere without network connectivity, you have a local copy of Ubuntu. Currently this only mirrors Ubuntu 16.04 Xenial and does not update the mirror after image creation.
Also provided is a Kubernetes Helm chart to deploy the MaaS pieces and integrates them. This chart depends on a previous deployment of Postgres. The recommended avenue for this is the Openstack Helm Postgres chart but any Postgres instance should work.
Chart overrides are likely required to deploy MaaS into your environment
During deployment, the chart executes the below steps: