Add option to specify a Pod's PriorityClass

[jangrewe]

I had to manually hardcode a priorityClassName in the code, as our cluster otherwise preempts the Pod during the rsync process.
It would be great if you could add an option to set that, or maybe even better: allow to specify a YAML template with all the bells and whistles that a Pod needs (labels, annotations, etc.) to be deployed successfully.

[laverya]

Supplying a pod template makes sense to not require a dozen features, but is there a good way to do that from the CLI?

passing in json/yaml is what I can think of, and that kind of sucks

[jangrewe]

I guess providing a YAML template trumps any other arguments one could wish for when creating a Pod, so i'd very much prefer that - also because i noticed a couple of labels and annotations that would be required to make a Pod a good citizen in our clusters. ;-)

Oh, and just to be sure: i'm talking about something like pvmigrate ... -template ./pod.yml

Maybe this is of help? https://medium.com/@harshjniitr/reading-and-writing-k8s-resource-as-yaml-in-golang-81dc8c7ea800

[laverya]

That does make sense!