Skip to content

Fix securityContext for pod #2623

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 2 commits into from
May 27, 2025
Merged

Fix securityContext for pod #2623

merged 2 commits into from
May 27, 2025

Conversation

ikreymer
Copy link
Member

@ikreymer ikreymer commented May 26, 2025

Some of the securityContext settings need to be on the container, not on the pod.
This enables the read-only file system.
Also map the crawler /tmp directory to use the same volume as crawls (as crawler currently uses /tmp dir)

@ikreymer ikreymer requested a review from tw4l May 26, 2025 19:53
Copy link
Member

@tw4l tw4l left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Tested with custom behaviors downloaded to /tmp and worked well.

@ikreymer ikreymer merged commit 5b0f851 into main May 27, 2025
22 checks passed
@ikreymer ikreymer deleted the fix-securitycontext-pod branch May 27, 2025 17:59
SuaYoo pushed a commit that referenced this pull request May 27, 2025
Some of the `securityContext` settings need to be on the container, not
on the pod, including the read-only file system, which was not previously enabled.
This now enables the read-only file system.
Also map the crawler /tmp directory to use the same volume as crawls (as
crawler currently uses /tmp dir) as /tmp becomes read-only otherwise.
ikreymer added a commit that referenced this pull request Jul 8, 2025
- don't use a persistent volume for /tmp, instead use a temporary
emptyDir
- use volume to avoid permission issues with default /tmp dir
- follow-up to #2623
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants