chore: add steps to validate pod templates

[ravisingal]

No description provided.

[abeytom07]

@ravisingal You need to override/disable in the other subcharts?

kstreams-app-version-checker:
  containerSecurityContext:
    {{ .tfi.containerSecurityContext | toYaml | nindent 4 }}
  podSecurityContext:
    {{ .tfi.podSecurityContext | toYaml | nindent 4 }}
  commonPodLabels:
    applicationid: ABCD1234

  commonPodAnnotations:
    applicationid: ABCD1234

podSecurityContext:
  {{ .tfi.podSecurityContext | toYaml | nindent 2 }}

containerSecurityContext:
  {{ .tfi.containerSecurityContext | toYaml | nindent 2 }}
  
hypertrace-pinot:
  containerSecurityContext:
    {{ .tfi.containerSecurityContext | toYaml | nindent 4 }}
  
  podSecurityContext:
    {{ .tfi.podSecurityContext | toYaml | nindent 4 }}  

redis:
  master:
    containerSecurityContext:
      {{ .tfi.containerSecurityContext | toYaml | nindent 6 }}
    
    podSecurityContext:
      {{ .tfi.podSecurityContext | toYaml | nindent 6 }}
  metrics:
    containerSecurityContext:
      {{ .tfi.containerSecurityContext | toYaml | nindent 6 }}      

config-bootstrapper:
  containerSecurityContext:
    {{ .tfi.containerSecurityContext | toYaml | nindent 4 }}
  
  podSecurityContext:
    {{ .tfi.podSecurityContext | toYaml | nindent 4 }}

db-schema-manager:
  enabled: false

postgresql:
  primary:
    containerSecurityContext:
      {{ .tfi.containerSecurityContext | toYaml | nindent 6 }}
    
    podSecurityContext:
      {{ .tfi.podSecurityContext | toYaml | nindent 6 }}
  metrics:
    containerSecurityContext:
      {{ .tfi.containerSecurityContext | toYaml | nindent 6 }}
    
    podSecurityContext:
      {{ .tfi.podSecurityContext | toYaml | nindent 6 }}      

commonPodLabels:
  applicationid: ABCD1234

commonPodAnnotations:
  applicationid: ABCD1234  

[abeytom07]

@ravisingal @aaron-steinfeld May be we need to support a custom override

uses: hypertrace/github-actions/validate-charts@main
with:
  chart-path: ./helm-test
  extra-values: |
     my-service:
        podSecuritycontext:
          runAsUser: 12345

Yes, the same can be done via extra args but this is easier. Otherwise, I would assume check-pod-template will be set to false everywhere. I think it will get the best of both worlds; fail if the mandatory properties cannot be set, at the same time it won't block on false positives.