Skip to content

fix: Clean up MetalLB pod security standards labels #807

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 16, 2024

Conversation

jimmidyson
Copy link
Member

@jimmidyson jimmidyson commented Jul 16, 2024

This commit removes the pod-security.kubernetes.io/audit and
pod-security.kubernetes.io/warn labels as they are redundant when
specifying the pod-security.kubernetes.io/enforce label to the same
level.

Also add the pod-security.kubernetes.io/enforce-version label to
always 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 the
latest policy version.

@github-actions github-actions bot added fix and removed fix labels Jul 16, 2024
@jimmidyson jimmidyson enabled auto-merge (squash) July 16, 2024 15:27
@github-actions github-actions bot added fix and removed fix labels Jul 16, 2024
This commit removes the `pod-security.kubernetes.io/audit` and
`pod-security.kubernetes.io/warn` labels as they are redundant when
specifying the `pod-security.kubernetes.io/enforce` label to the same
level.

Also add the `pod-security.kubernetes.io/enforce-version` label to
always enforce the latest pod security polify version, even on upgrade.
This is fine because we are specifying the omst privileged pod security
standard, `privileged`, and as such should be safe to always enfore the
latest policy version.
@jimmidyson jimmidyson force-pushed the jimmi/service-lb-pod-security branch from 771f281 to a604c90 Compare July 16, 2024 17:34
@dlipovetsky
Copy link
Contributor

Thanks. Really wish these could be managed together with the Chart.

@jimmidyson jimmidyson merged commit 7e04852 into main Jul 16, 2024
15 checks passed
@jimmidyson jimmidyson deleted the jimmi/service-lb-pod-security branch July 16, 2024 23:45
@github-actions github-actions bot mentioned this pull request Jul 16, 2024
jimmidyson added a commit that referenced this pull request Jul 18, 2024
🤖 I have created a release *beep* *boop*
---


## 0.13.0 (2024-07-18)

<!-- Release notes generated using configuration in .github/release.yaml
at main -->

## What's Changed
### Exciting New Features 🎉
* feat: Secure ciphers, min TLS v1.2, and disable auto TLS for etcd by
@jimmidyson in
#808
* feat: Bump default k8s version for tests to v1.29.6 by @jimmidyson in
#784
### Fixes 🔧
* fix: add omitempty to addon strategy by @dkoshkin in
#795
* fix: update CCM to 0.3.4 to fix sweet32 issue by @tuxtof in
#805
* fix: Clean up MetalLB pod security standards labels by @jimmidyson in
#807
* fix: Fix ownership of ClusterAutoscaler resources by @jimmidyson in
#810
### Other Changes
* ci: Run e2e jobs only if unit-test, lint-*, and pre-commit jobs pass
by @dlipovetsky in
#796
* ci: Enable verbose output for e2e tests by @dlipovetsky in
#797
* test: Verify ServiceLoadBalancer in e2e Docker and Nutanix tests by
@dlipovetsky in
#788
* refactor: Use CAPI conditions check where possible by @dlipovetsky in
#789
* test(e2e): Use parallel tests for providers other than Docker by
@jimmidyson in
#787

## New Contributors
* @tuxtof made their first contribution in
#805

**Full Changelog**:
v0.12.1...v0.13.0

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants