Skip to content
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

Add explicit security context capability for compatibility with cri-o #621

Merged
merged 1 commit into from
Jul 15, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGES.rst
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,8 @@ Unreleased

* Changed the ``node.attr.zone`` parameter for AWS to use IMDSv2.

* Added explicit security context capabilities for compatibility with cri-o.

2.39.0 (2024-05-22)
-------------------

Expand Down
4 changes: 4 additions & 0 deletions crate/operator/create.py
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,7 @@
CoreV1Api,
PolicyV1Api,
V1Affinity,
V1Capabilities,
V1ConfigMap,
V1ConfigMapVolumeSource,
V1Container,
Expand Down Expand Up @@ -363,6 +364,9 @@ def get_statefulset_containers(
},
),
volume_mounts=crate_volume_mounts,
security_context=V1SecurityContext(
capabilities=V1Capabilities(add=["SYS_CHROOT"])
),
),
]

Expand Down
Loading