Adding more optional parameters

[hamedhsn]

Provide a capability to pass a few options when running job

• job_name
• image_pull_policy
• restart_policy

---

This change is 

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: r2d4

If they are not already assigned, you can assign the PR to them by writing /assign @r2d4 in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @hamedhsn. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[wbuchwalter]

Do we really want this to be controlled at the user level?
Fairing shouldn't expose all possible parameters that are available on the pod/job spec.
Could this be just solved by sane default in the builder?
If there is really a need for customization, could this be solved with the admin config (#28) instead?

[hamedhsn]

hmm.. I see.
configmap make sense for really admin stuff like image_pull_policy or restart policy, however, users might want to pick the name for their jobs. This will make it easier once multiple users submit different jobs. Based on my observation, in most of the case names are chosen meaningful to the experiments.
Any further operations make it easier once it has a custom name.

[jlewi]

/assign @r2d4
/unassign @richardsliu

[hamedhsn]

closing this as it is old and was before major refactoring.