feat: add support to configure securityContext

[Falltrades]

Following the logic of this PR : #1695 to avoid error such as the one below when deploying on an Openshift cluster.

.spec.securityContext.fsGroup: Invalid value: []int64{10000}: 10000 is not an allowed group, provider restricted-v2: .containers[0].runAsUser: Invalid value: 10000: must be in the ranges: [1000870000, 1000879999]

Example test:

helm template . --set metrics.enabled=true --set securityContext="" --show-only templates/exporter/
exporter-dpl.yaml 

[MinerYang]

Hi @Falltrades ,

which helm version you are using?
FIY we already support set container securityContext since helm 1.15.0

harbor-helm/values.yaml

Line 471 in d218b4d

## containerSecurityContext:{} is initially an empty yaml that you could edit it on demand, we just filled with a common template for convenience

[Falltrades]

Hi @MinerYang,
I am currently using 1.16.0 chart version. Indeed containerSecurityContext is supported, but it seems we need support for securitycontext as well.

[MinerYang]

Hi @MinerYang, I am currently using 1.16.0 chart version. Indeed containerSecurityContext is supported, but it seems we need support for securitycontext as well.

We would prefer officially support container-level security-context instead of pod-level ones. And it override settings made at the Pod level when there is overlap.

So if you still have requirement for pod-level security context, I would suggest you to fork and customize your templates

Best,
Miner

[Falltrades]

Actually, it is more like about wanting to unset pod-level security context, because right now we can't. Is Harbor deployment on OpenShift no longer supported by this helm chart ?

[Falltrades]

My bad, I got it now, it seems like harbor-exporter deployment is missing serviceAccount compare to the others in my values.