Skip to content
This repository has been archived by the owner on Jan 18, 2024. It is now read-only.

Missing securityContext to fulfil podSecurityPolicy requirements #124

Open
juusujanar opened this issue Feb 26, 2020 · 1 comment
Open
Labels
area/timescaledb-single bug Something isn't working enhancement New feature or request

Comments

@juusujanar
Copy link

I have been trying to get this deployed to my cluster, however I need to manually re-add securityContext sections to numerous containers because I am using Pod Security Policy to ensure all containers are running as non-root.

Some examples include, but not limited to:

  • initContainer tstune
  • container timescaledb
  • container pgbackrest
  • backup cronJob timescaledb-full-daily
  • backup cronJob timescaledb-incremental-hourly

I'm happy to assist with the configuration and creating a PR, however I am not sure about Helm best practices here. If the image can be changed in values.yaml, so should be the securityContext values, right?

@rushabh-harness
Copy link

I am facing the same issue so +1 on this solution if that helps solve the problem

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/timescaledb-single bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants