Container security context

Bug

Description

Harbor is not creating it's deployments with containerSecurityContext properly.

Line 61 tries to use the global scope of the values file, but in line 59 the scope is change to where the "." would be equal to ".Values.exporter.containerSecurityContext".

Line 61 should be the following

          {{- toYaml $. | nindent 10 }}

Instead, the path resolves to a global path of .Values.exporter.containerSecurityContext.Values.exporter.containerSecurityContext which doesn't exist.

So, line 60 ends up standing alone, assigned to a null value, and our deployment manifest ends up looking like this:

BigBang Version

2.20.0