Register plugins with the scheduling framework properly

[y-taka-23]

What type of PR is this?
/kind bug

What this PR does / why we need it:

Currently the functions for plugin registration are in the passing-by-value. In my understanding, we should pass references here not to discard the changes at the end of the function scope.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Fix registration for scheduling framework plugins with the default plugin set

/sig scheduling

[k8s-ci-robot]

Hi @y-taka-23. Thanks for your PR.

I'm waiting for a kubernetes 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.

[yastij]

/ok-to-test

[Huang-Wei]

/lgtm

Agree. It should be using a "pointer receiver" as its data is modified (initialized).

[yastij]

/lgtm

[yastij]

@y-taka-23 - can you also refactor the example plugins ? Some of these have the same problem.

[k82cn]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: k82cn, y-taka-23

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 [k82cn]

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

[y-taka-23]

@yastij I apologize for the late reply.

Perhaps we have no problem with the example plugins; already StatefulMultipointExample is used as a pointer receiver.