Allow MetalLB's privileged networking Pods via namespace Pod Security labels
This commit is contained in:
@@ -34,5 +34,14 @@ spec:
|
|||||||
automated:
|
automated:
|
||||||
prune: true
|
prune: true
|
||||||
selfHeal: true
|
selfHeal: true
|
||||||
|
# MetalLB's speaker and FRR Pods use host networking and Linux network
|
||||||
|
# capabilities so they can establish BGP sessions. Kubernetes' baseline
|
||||||
|
# Pod Security policy rejects those by design; privilege is scoped to this
|
||||||
|
# dedicated namespace rather than weakened cluster-wide.
|
||||||
|
managedNamespaceMetadata:
|
||||||
|
labels:
|
||||||
|
pod-security.kubernetes.io/enforce: privileged
|
||||||
|
pod-security.kubernetes.io/audit: privileged
|
||||||
|
pod-security.kubernetes.io/warn: privileged
|
||||||
syncOptions:
|
syncOptions:
|
||||||
- CreateNamespace=true
|
- CreateNamespace=true
|
||||||
|
|||||||
Reference in New Issue
Block a user