Sphicas, Phil (ps3910) 938c6d9bb9 fix: ceph-osd AppArmor profiles not applied
AppArmor annotations require the container name to be applied properly.
Before this change, when overrides are not used, the container name is
ceph-osd-default. When overrides are used, the container name is of the
form ceph-osd-HOSTNAME-SHA, but with an identical HOSTNAME and SHA for
all the daemonsets. However, it is not possible to predict this value,
and as a result, the AppArmor profiles are not applied.

This change removes the customization of the container name, and sets
it to ceph-osd-default, allowing AppArmor annotations to be consistently
applied using:

    pod:
      mandatory_access_control:
        type: apparmor
        ceph-osd-default:
          ceph-osd-default: localhost/profilename

Change-Id: I8b6eda00f77ec7393a4311309f3ff76908d06ae6
2019-11-06 14:48:12 +00:00
2019-10-10 15:47:20 +08:00
2019-10-23 19:16:28 +00:00
2019-10-23 19:16:28 +00:00
2019-10-21 18:27:41 +00:00
2019-10-21 18:27:41 +00:00
2019-09-11 12:46:34 +04: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 126 MiB
Languages
Smarty 82.3%
Shell 16%
Python 1.3%
Jinja 0.2%
Makefile 0.2%