add labels, securityContext and image pull secret in cluster controller

[mittal-ishaan]

What does this PR change?

Adds Labels, SecurityContext and image pull secrets to cluster controller configurations.

Does this PR rely on any other PRs?

No

How does this PR impact users? (This is the kind of thing that goes in release notes!)

Users will now be able to add:

• custom labels to the deployment and pod.
• Security context at the pod and container level
• image pull secret to cluster controller pod

Links to Issues or tickets this PR addresses or fixes

No

What risks are associated with merging this PR? What is required to fully test this PR?

No

How was this PR tested?

When setting imagePullSecret, labels and securityContext. We get the following deployment template using helm template

# Source: cost-analyzer/templates/kubecost-cluster-controller-template.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: cost-analyzer-cluster-controller
  namespace: default
  labels:
    app.kubernetes.io/name: cost-analyzer
    helm.sh/chart: cost-analyzer-2.3.3
    app.kubernetes.io/instance: cost-analyzer
    app.kubernetes.io/managed-by: Helm
    app: cost-analyzer
    hey: there
  annotations:
spec:
  strategy:
    rollingUpdate:
      maxSurge: 1
      maxUnavailable: 1
    type: RollingUpdate
  selector:
    matchLabels:
      app: cost-analyzer-cluster-controller
  template:
    metadata:
      labels:
        app: cost-analyzer-cluster-controller
        hey: there
    spec:
      securityContext:
        fsGroup: 1001
        fsGroupChangePolicy: OnRootMismatch
        runAsGroup: 1001
        runAsNonRoot: true
        runAsUser: 1001
        seccompProfile:
          type: RuntimeDefault
      containers:
      - name: cost-analyzer-cluster-controller
        image: gcr.io/kubecost1/cluster-controller:v0.16.11
        imagePullPolicy: IfNotPresent
        securityContext:
          hey: there
        volumeMounts:
        - name: cluster-controller-keys
          mountPath: /var/keys
        env:
          ...
        ports:
        - name: http-server
          containerPort: 9731
          hostPort: 9731
        resources:
            {}
      imagePullSecrets:
        - name: image-pull-secret
      serviceAccount: cost-analyzer-cluster-controller
      serviceAccountName: cost-analyzer-cluster-controller
      volumes:
        ...

deployed kubecost using these configurations

Have you made an update to documentation? If so, please provide the corresponding PR.

No

[thomasvn]

Thanks for these updates, and for providing the results when templating using these new values. The changes here align with how cost-analyzer-deployment.yaml sets these values. LGTM!