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

Support running with read-only root filesystem #240

Open
howardburgess opened this issue Oct 25, 2021 · 0 comments
Open

Support running with read-only root filesystem #240

howardburgess opened this issue Oct 25, 2021 · 0 comments

Comments

@howardburgess
Copy link
Contributor

howardburgess commented Oct 25, 2021

Feed-ingress does not currently support running with the following securityContext setting, which would help to increase the security of the running container.

kind: Pod
spec:
  containers:
  - securityContext:
      readOnlyRootFilesystem: true`

feed-ingress writes to (at least):

  • /var/log/nginx (or wherever --access-log-dir points)
  • /tmp
  • /nginx/nginx.conf
  • /nginx/nginx.tmpl

The first two are directories and hence an EmptyDir can be mounted for them, for example. The NGINX config and the template are individual files that live in the main /nginx directory along with other required files, hence can't be volume-mounted.

Simply using a mountable directory for the NGINX config (e.g. /nginx/conf/) might be sufficient to allow running with readOnlyRootFilesystem: true (kubesec.io docs). However, we should also check what other files feed-ingress or NGINX might write to.

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

No branches or pull requests

1 participant