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 securityContext to provided Kubernetes manifest #859

Merged
merged 1 commit into from
Mar 23, 2024

Conversation

piano1029
Copy link
Contributor

In the (currently) provided Kubernetes deployment manifest the securityContext is missing, this results in Shiori crashing with a vague "out of memory" error. This pull request adds the securityContext with the same uid and gid values as in the Docker image (1000), fixes #791.

Copy link

codecov bot commented Mar 17, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 25.58%. Comparing base (595cb45) to head (dc3760b).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #859   +/-   ##
=======================================
  Coverage   25.58%   25.58%           
=======================================
  Files          47       47           
  Lines        5628     5628           
=======================================
  Hits         1440     1440           
  Misses       3989     3989           
  Partials      199      199           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@fmartingr fmartingr merged commit 21c95ac into go-shiori:master Mar 23, 2024
10 checks passed
@fmartingr
Copy link
Member

Hey @piano1029, thanks for the contribution. I will probably update the deployment docs with a link to an helm chart instead of having that YAML around, the docs require some love in all areas. Thanks for catching this.

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.

security context is necessary for Kubernetes
2 participants