[PTP] Update notification namespace to be privileged
The ptp-notification application requires a privileged namespace in
order to deploy and operate.
This change moves the notification namespace from the baseline policy
group to the privileged policy group so that it can continue to operate
as it did prior to the addition of support for the Pod Security
Admission controller introduced in the upversion to k8s 1.23.
Reviewed: https:/ /review. opendev. org/c/starlingx /config/ +/845852 /opendev. org/starlingx/ config/ commit/ b50407b5fa303c3 3f0e18bb3394e08 5adb82efd2
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit b50407b5fa303c3 3f0e18bb3394e08 5adb82efd2
Author: Cole Walker <email address hidden>
Date: Tue Jun 14 17:50:21 2022 -0400
[PTP] Update notification namespace to be privileged
The ptp-notification application requires a privileged namespace in
order to deploy and operate.
This change moves the notification namespace from the baseline policy
group to the privileged policy group so that it can continue to operate
as it did prior to the addition of support for the Pod Security
Admission controller introduced in the upversion to k8s 1.23.
The privileged and baseline groups were defined in /review. opendev. org/c/starlingx /config/ +/833487
https:/
Test-plan:
Pass: Update the privileged and baseline groups in common.py, restart conductor and verify that ptp-notification is able to properly
sysinv-
deploy.
Pass: Verify that the notification namespace has the expected
privileged labels.
Closes-Bug: 1978737
Signed-off-by: Cole Walker <email address hidden> 9f568a5953701cf 2e0c474005e
Change-Id: I5d24a8e81b3280