add rest config into ssn

[wpeng102]

Signed-off-by: wpeng102 wpeng102@126.com

Customer maybe introduce CRD resource for scheduling. So in scheduler plugin, customer maybe need construct this CRD's informer. Currently ssn only provide kubeclient for plugin, we need provide restconfig for customer to init customer resource client.

[Thor-wl]

Sound reasonable.That's OK for me.
/lgtm

[elinx]

The plugins are created and destroyed each scheduling cycle, do you recreate the informers every time?

If it's not, do you think it's a good option to put these informer creations somewhere before the session starts?

[wpeng102]

The plugins are created and destroyed each scheduling cycle, do you recreate the informers every time?

If it's not, do you think it's a good option to put these informer creations somewhere before the session starts?

Good question. Currently volcano plugin does not provide a informer function which can init the informer. I think customer can use a singleton function to init some variable to avoid recreate every scheduler period.

[william-wang]

/approve

[volcano-sh-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: william-wang

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:

• pkg/scheduler/OWNERS [william-wang]

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