node: cpumgr: rename CPUManager KEP 375 -> 3570

Rename the KEP number for consistency with the k/enhancements ID.

This is done *only* for the GA graduation; great care was taken
to ensure the original content is preserved and the updates are
applied incrementally with clearly separated steps.

Rationale for the rename:
- the original enhancement was unchanged for many years and closed;
- however the feature was beta for 16 releases (1.10 -> 1.26+) and
  needs a nontrivial amount of work and updates for the GA graduation
  step.
- it's more practical to handle the GA graduation stage with its own
  enhancement.`

Signed-off-by: Francesco Romani <[email protected]>

Author: ffromani

keps/prod-readiness/sig-node/375.yaml renamed to keps/prod-readiness/sig-node/3570.yaml

@@ -1,4 +1,4 @@
-kep-number: 375
+kep-number: 3570
 alpha:
   approver: "@deads2k"
 beta:

keps/sig-node/375-cpu-manager/README.md renamed to keps/sig-node/3570-cpumanager/README.md

@@ -104,6 +104,7 @@ This new method is invoked from two places in the CPU manager: during each
 call to `AddContainer` and also periodically from a separate
 reconciliation loop.
 
+This KEP supersedes and replaces `kubernetes/enhancements/keps/sig-node/375-cpumanager/README.md`.
 
 ## Motivation
 

keps/sig-node/375-cpu-manager/kep.yaml renamed to keps/sig-node/3570-cpumanager/kep.yaml

@@ -1,5 +1,5 @@
 title: CPU Manager
-kep-number: 375
+kep-number: 3570
 authors:
   - "@ConnorDoyle"
   - "@flyingcougar"
@@ -14,11 +14,12 @@ approvers:
   - "@derekwaynecarr"
 editor: Connor Doyle, Francesco Romani (only for the GA graduation)
 creation-date: 2017-05-23
-last-updated: 2017-05-23
+last-updated: 2022-10-03
 status: implementable
 see-also:
 replaces:
-  - " kubernetes/community/contributors/design-proposals/node/cpu-manager.md"
+  - "kubernetes/community/contributors/design-proposals/node/cpu-manager.md"
+  - "kubernetes/enhancements/keps/sig-node/375-cpumanager/README.md"
 superseded-by:
 
 # The target maturity stage in the current dev cycle for this KEP.