scheduler: make history-sample-interval and history-sample-duration configurable (#7878)

[ti-chi-bot]

This is an automated cherry-pick of #7878

What problem does this PR solve?

Issue Number: Close #7877

What is changed and how does it work?

Check List

Tests

• Unit test

• Integration test

• Manual test (add detailed scripts or steps below)

• Has the configuration change

Release note

None.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• HuSharp
• nolouch

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[lhy1024]

/retest

[lhy1024]

/test build

[codecov]

Codecov Report

Merging #7893 (16b6345) into release-7.5 (8783927) will increase coverage by 0.06%.
Report is 3 commits behind head on release-7.5.
The diff coverage is 88.60%.

Additional details and impacted files

@@               Coverage Diff               @@
##           release-7.5    #7893      +/-   ##
===============================================
+ Coverage        74.51%   74.57%   +0.06%     
===============================================
  Files              444      444              
  Lines            48156    48247      +91     
===============================================
+ Hits             35883    35982      +99     
+ Misses            9079     9074       -5     
+ Partials          3194     3191       -3     

Flag	Coverage Δ
unittests	74.57% <88.60%> (+0.06%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[nolouch]

/merge

[ti-chi-bot]

@nolouch: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

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 ti-community-infra/tichi repository.

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 68a2151

[ti-chi-bot]

@ti-chi-bot: Your PR was out of date, I have automatically updated it for you.

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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 ti-community-infra/tichi repository.

[lhy1024]

/hold

[lhy1024]

Do we need to merge it to release 7.5? It's provided to special user.

[nolouch]

IMO, no need.

[ti-chi-bot]

This cherry pick PR is for a release branch and has not yet been approved by triage owners.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick:

1. It must be approved by the approvers firstly.
2. AFTER it has been approved by approvers, please wait for the cherry-pick merging approval from triage owners.

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.