Shane McDonald 423df6618d Force containers in k8s to run under root group ...

Normally containers belong to the 'root' group, but for some reason the
downstream red hat scl redis image only belongs to the 'redis' group by default. This fixes that.

2020-06-10 13:40:15 -04:00

..

configmap.yml.j2

Force containers in k8s to run under root group

2020-06-10 13:40:15 -04:00

credentials.py.j2

autogenerate websocket secret

2020-03-26 10:32:37 -04:00

deployment.yml.j2

Force containers in k8s to run under root group

2020-06-10 13:40:15 -04:00

environment.sh.j2

switch memcached from tcp to unix domain socket

2020-04-06 08:35:12 -04:00

launch_awx.yml.j2

Make supervisor more consistent

2020-06-02 19:51:16 -04:00

management-pod.yml.j2

add CA trust volume to management pod

2020-04-27 13:01:32 -04:00

postgresql-persistent.yml.j2

Pull in downstream changes to k8s installer

2019-12-02 08:12:51 -05:00

postgresql-values.yml.j2

Configurable image registry and service account for Postgres deployment.

2019-11-20 14:15:59 +01:00

secret.yml.j2

Initial migration of rabbitmq -> redis for k8s installs

2020-03-18 16:10:17 -04:00

supervisor.yml.j2

Make supervisor more consistent

2020-06-02 19:51:16 -04:00