add edited clamav chart with podSecurityContext: {}

[gislab-augsburg]

In the OpenShift environment at Landeshauptstadt München (LHM) we are restricted from using predefined users or groups. The clamav subchart values for PodSecurityContext , runAsUserand runAsGroup cannot be updated via values.yaml to {} or Null because of an unresolved helm issue.

Our workaround is to add the edited clamav chart directly to the repo instead of pulling it from wiremind. The only changed value is PodSecurityContext: https://github.com/it-at-m/sddi-ckan-k8s/blob/46f8e82d4cdf712b2ab255774fb0dc5d5f74a88e/charts/sddi-ckan/charts/clamav/values.yaml#L30

[BWibo]

@gislab-augsburg
The issue is the same as we resolved it in #32 for the initContainers etc., right?
Copying the entire chart is not ideal, as this brings us in the position to keep maintaining this. Maybe we could try submitting a PR to wiremind, introducing the solution we used in #32.

[gislab-augsburg]

@BWibo
Yes, it is similar to part of the issue we resolved in #32. The difference is that we do not have init containers which we can simply replace in the wiremind chart. And also I am not sure if this would help because the clamav user is maybe also needed during runtime.
What do you think about the following little change we could submit as PR to wiremind?
gislab-augsburg/wiremind-helm-charts@e858abc

[gislab-augsburg]

I updated to the current version of the wiremind helm chart because LHM IT-Security prefers the original clamav/clamav image over ghcr.io/mailu/clamav and with the current wiremind version we could resolve another permission issue we had with the clamav/clamav image with entrypoint: /init-unprivileged.