Go to file
Alexander Noskov d9b939979d Ingress: Fix security context for pod/container
During armada bootstrap, ingress pod tries to execute chroot [0]
inside root directory on host machine to load dummy kernel module
and getting permission denied error.

[0] https://opendev.org/openstack/openstack-helm-infra/src/branch/master/ingress/templates/bin/_ingress-vip-routed.sh.tpl#L22

Change-Id: Icf7e29e95e0c3cf2bf71a22711a03218390c90cb
2019-06-14 17:24:42 +00:00
2019-05-23 23:06:11 +00:00
2019-05-28 08:23:44 -05:00
2019-04-20 20:50:59 +00:00
2019-05-14 17:04:52 -05:00
2019-06-05 16:57:40 +00:00
2019-05-17 08:17:32 +00:00
2019-05-14 17:04:52 -05:00
2019-04-19 19:34:11 +00:00
2019-02-27 15:02:06 +08:00
2018-05-15 13:04:28 -05:00

Openstack-Helm-Infra

Mission

The goal of OpenStack-Helm-Infra is to provide charts for services or integration of third-party solutions that are required to run OpenStack-Helm.

For more information, please refer to the OpenStack-Helm repository.

Communication

  • Join us on Slack - #openstack-helm
  • Join us on IRC: #openstack-helm on freenode
  • Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-4 on freenode
  • Meeting Agenda Items: Agenda

Launchpad

Bugs and blueprints are tracked via OpenStack-Helm's Launchpad. Any bugs or blueprints filed in the OpenStack-Helm-Infra Launchpad will be closed and requests will be made to file them in the appropriate location.

Description
Helm charts for deploying OpenStack on Kubernetes
Readme 129 MiB
Languages
Smarty 81.2%
Shell 16.9%
Python 1.4%
Jinja 0.3%
Makefile 0.2%