KEP-4951: Add PRR file.

[jm-franc]

Add files needed to start the PRR process.

Issue link.

[k8s-ci-robot]

Hi @jm-franc. 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-sigs/prow repository.

[jm-franc]

/cc @deads2k

[jm-franc]

/assign @gjtempleton

[jm-franc]

/hold

[To ensure this isn't automatically merged before both PRR and SIG lead reviewed.]

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jm-franc
Once this PR has been reviewed and has the lgtm label, please ask for approval from gjtempleton and additionally assign deads2k for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• keps/prod-readiness/OWNERS
• keps/sig-autoscaling/OWNERS

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

[adrianmoisey]

LGTM

[raywainman]

/ok-to-test

[gjtempleton]

Couple of questions from me.

[gjtempleton]

Would this be enough to tell users that it was scaling using the configured, non-global level tolerance?

Feel like this falls under the same challenge as linked out to in the missing metrics section.

[gjtempleton]

Can we provide more detail here - do we have an idea of what signals they might be able to look at - would they need to do some maths to check the tolerance level being applied, or do we foresee some debug level logging being available with this information?