#1831 [BUG] flyescheduler should use its own service account Issue created by pmahindrakar-oss Describe the bug flytescheduler uses flyteadmin service account which is incorrect.

kubectl get pod/flytescheduler-8785896b8-27b52 -n flyte  -o yaml |less                 
.......

    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /etc/flyte/config
      name: config-volume
    - mountPath: /etc/secrets/
      name: auth
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: flyteadmin-token-79jmm
      readOnly: true
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  initContainers:
  - command:
    - flytescheduler
    - precheck
    - --config
    - /etc/flyte/config/*.yaml
    image: <http://cr.flyte.org/flyteorg/flytescheduler:v0.6.49|cr.flyte.org/flyteorg/flytescheduler:v0.6.49>
    imagePullPolicy: IfNotPresent
    name: flytescheduler-check
    resources: {}
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /etc/flyte/config
      name: config-volume
    - mountPath: /etc/secrets/
      name: auth
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: flyteadmin-token-79jmm
      readOnly: true
  nodeName: docker-desktop
  preemptionPolicy: PreemptLowerPriority
  priority: 0
  restartPolicy: Always
  schedulerName: default-scheduler
  securityContext: {}
  serviceAccount: flyteadmin
  serviceAccountName: flyteadmin

Expected behavior flytescheduler should use its own service account Additional context to reproduce No response Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte