My team and I are currently working on a project where we are trying to deploy Dependency-Track on a managed AKS cluster using this Helm chart. However, the security context currently seems to be too restrictive and it is causing issues with configuration via the config.json.
We would therefore propose the addition of the securityContext key for the frontend and the api-server as there might be more use cases for this property to be overridable. The values currently configured in the templates would then become default values.
Hi,
My team and I are currently working on a project where we are trying to deploy Dependency-Track on a managed AKS cluster using this Helm chart. However, the security context currently seems to be too restrictive and it is causing issues with configuration via the
config.json
.We would therefore propose the addition of the
securityContext
key for the frontend and the api-server as there might be more use cases for this property to be overridable. The values currently configured in the templates would then become default values.