imgproxy-helm

imgproxy-helm copied to clipboard

As described here: https://helm.sh/docs/chart_best_practices/labels/#standard-labels

jyoungs

The imgproxy Helm chart doesn't support container-level SecurityContext. This prevents the usage of read-only filesystem for example as the pod security context and container security context are different. See the...

SimonWoidig

feat: Add custom settings for pod- and containerSecurityContext instead of global securityContext

3

this one was merged in a custom branch and never got it into master so new try (https://github.com/imgproxy/imgproxy-helm/pull/157)

kaufmo

refactor: use image.repository instead of abbreviation

2

tools like renovate can update the combination of repository & tag see [here](https://docs.renovatebot.com/modules/manager/helm-values/) for more details

kaufmo

@DarthSim has just updated the [Configuration](https://docs.imgproxy.net/configuration/options) part of the documentation. Please, check [the difference](https://github.com/imgproxy/imgproxy-docs/compare/5100fdb0bd61...7be33a2b9121) and make the necessary changes in the Helm chart.

github-actions[bot]

when deploy imgproxy with and persistance mount the local_filesystem_root must be set manual. ```yaml imgproxy: features: urlSignature: enabled: true key: xxxx salt: xxxx prometheus: enabled: true custom: IMGPROXY_LOCAL_FILESYSTEM_ROOT: /images #

spelbreker