Description of problem:
aws-load-balancer-controller-cluster pod logged Podsecurity violation error during deployment as below

1.6526850318382206e+09	INFO	KubeAPIWarningLogger	would violate PodSecurity "restricted:latest": allowPrivilegeEscalation != false (container "controller" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "controller" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or container "controller" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container "controller" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")



OpenShift release version:
4.11.0-0.nightly-2022-05-11-054135

Cluster Platform:
AWS

How reproducible:
100%

Steps to Reproduce (in detail):
1. install aws-load-balancer-operator via OperatorHub
2. create AWSLoadBalancerController resource
3. check the aws-load-balancer-operator pod logs
$ oc -n aws-load-balancer-operator logs aws-load-balancer-operator-controller-manager-9bc7f96b6-kp9gd -c manager


Actual results:
see Podsecurity violation error logs

Expected results:
should not occur

Impact of the problem:


Additional info:
This appears to be due to the PodSecurity feature gate being active by default for v1.23 k8s release and from 4.11 pod security admission level gets set as "restricted" by default. Ref: https://kubernetes.io/docs/concepts/security/pod-security-admission/

see also: https://issues.redhat.com/browse/AUTH-133


** Please do not disregard the report template; filling the template out as much as possible will allow us to help you. Please consider attaching a must-gather archive (via `oc adm must-gather`). Please review must-gather contents for sensitive information before attaching any must-gathers to a bugzilla report.  You may also mark the bug private if you wish.