You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: changelog/20250924_fix_provide_more_secure_pod_and_container.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,11 +4,14 @@ date: 2025-09-24
4
4
---
5
5
6
6
* To follow the [Pod Security Standards](https://v1-32.docs.kubernetes.io/docs/concepts/security/pod-security-standards/) more secure default pod `securityContext` settings were added.
7
-
8
-
Operator deployment `securityContext` settings that have changed:
7
+
Operator deployment `securityContext` settings that have changed:
9
8
-`allowPrivilegeEscalation: false`
10
9
-`capabilities.drop: [ ALL ]`
11
10
-`seccompProfile.type: RuntimeDefault`
12
11
13
12
Other workloads:
14
-
-`capabilities.drop: [ ALL ]`
13
+
-`capabilities.drop: [ ALL ]` - container level
14
+
-`seccompProfile.type: RuntimeDefault` - pod level
15
+
16
+
> **Note**: If you require less restrictive `securityContext` settings please use `template` or `podTemplate` overrides.
17
+
> Detailed information about overrides can be found in [Modify Ops Manager or MongoDB Kubernetes Resource Containers](https://www.mongodb.com/docs/kubernetes/current/tutorial/modify-resource-image/).
0 commit comments