I am still not sure if I good understood your question.

However, kubectl doesn't have an option to pass user or service account when creating jobs:

kubectl create job --help

Create a job with the specified name.

Examples:
  # Create a job
  kubectl create job my-job --image=busybox

  # Create a job with command
  kubectl create job my-job --image=busybox -- date

  # Create a job from a CronJob named "a-cronjob"
  kubectl create job test-job --from=cronjob/a-cronjob

Options:
      --allow-missing-template-keys=true: If true, ignore any errors in templates when a field or
map key is missing in the template. Only applies to golang and jsonpath output formats.
      --dry-run=false: If true, only print the object that would be sent, without sending it.
      --from='': The name of the resource to create a Job from (only cronjob is supported).
      --image='': Image name to run.
  -o, --output='': Output format. One of:
json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-file.
      --save-config=false: If true, the configuration of current object will be saved in its
annotation. Otherwise, the annotation will be unchanged. This flag is useful when you want to
perform kubectl apply on this object in the future.
      --template='': Template string or path to template file to use when -o=go-template,
-o=go-template-file. The template format is golang templates
[http://golang.org/pkg/text/template/#pkg-overview].
      --validate=true: If true, use a schema to validate the input before sending it

Usage:
  kubectl create job NAME --image=image [--from=cronjob/name] -- [COMMAND] [args...] [flags]
[options]

Use "kubectl options" for a list of global command-line options (applies to all commands).

You can specify many factors inside your YAML definition. For example you could create ServiceAccount or specify runAsUser in a pod configuration. However, this requires to have a definition file instead of run-level with kubectl.

Here you can find how to do it with runAsUser parameter.

You could also consider using ServiceAccount. Here you have article which might help you. However you would need to create specific ServiceAccount It would look similar like:

apiVersion: v1
kind: Pod
metadata:
   name: pod-demo-sa
spec:
   serviceAccountName: demo-sa
   containers:
   — name: alpine
     image: alpine:3.9
     command:
     — "sleep"
     — "10000"

If this would be for some labs or practice you could also think about creating customized docker image using Dockerfile.

Unfortunately previous options are hardcoded. Other solution would need a specific scritp and many pipelines.

In addition, as you mentioned in title, to pass some values to configuration you can use ConfigMap.