Bug 2134308

Summary: Add labels for pod security in the e2e test namespaces
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: N Balachandran <nibalach>
Component: lvm-operatorAssignee: N Balachandran <nibalach>
Status: CLOSED CURRENTRELEASE QA Contact: Aviad Polak <apolak>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.12CC: apolak, jolmomar, lgangava, muagarwa, ocs-bugs, odf-bz-bot, sapillai
Target Milestone: ---   
Target Release: ODF 4.12.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.12.0-79 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-08 14:06:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description N Balachandran 2022-10-13 06:46:02 UTC 
Description of problem (please be detailed as possible and provide log
snippests):
Pod Security Admission is enabled in OCP 4.12. As the default value prevents the operator and test pods from coming up in the namespaces, we need to set the "pod-security.kubernetes.io/enforce" label to "privileged".

Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. 
2.
3.


Actual results:


Expected results:


Additional info:
The changes are limited to the e2e code and will not impact QE.