shipyard/charts/shipyard
Rick Bartra 9eb430566b Make airflow-worker containers non-privileged
The 'airflow-worker' and 'airflow-logrotate' containers do not need to
run as privileged containers to perform their jobs. Shipyard deploy_site
action was used to test the 'airflow-worker' as a deploy_site invokes
'airflow-worker'. When performing deploy_site action, all steps succeeded
and the 'airflow-worker' shows no errors when 'airflow-worker' is
non-privileged.

When 'airflow-logrotate' runs as non-privileged, the 'airflow-logrotate'
container still logs correctly and is able to delete/rotate logs without
problems.

Note: Making airflow-worker run with non-privileged containers means that
these containers will use the docker-default apparmor profile by default.

Change-Id: I26eda3eb8b7a36e67c2e7b593326f1d063600fc3
2018-09-27 15:14:20 -04:00
..
templates Make airflow-worker containers non-privileged 2018-09-27 15:14:20 -04:00
.helmignore Update DryDock Operator & Shipyard Chart 2017-10-24 01:53:58 +00:00
Chart.yaml Fix: various documentation and URL fixes 2018-09-24 12:53:27 +02:00
requirements.yaml Change banners to restore attribution 2018-03-15 16:57:20 -05:00
values.yaml Merge "Add relabel_nodes action" 2018-09-25 20:50:04 +00:00