fix: Clean up MetalLB pod security standards labels #807
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit removes the
pod-security.kubernetes.io/audit
andpod-security.kubernetes.io/warn
labels as they are redundant whenspecifying the
pod-security.kubernetes.io/enforce
label to the samelevel.
Also add the
pod-security.kubernetes.io/enforce-version
label toalways enforce the latest pod security policy version, even on upgrade.
This is fine because we are specifying the most privileged pod security
standard,
privileged
, and as such should be safe to always enforce thelatest policy version.