add kms as to 1.26 rules for multiple components

[dims]

In 576cca0, we fixed one spot, looks like we need to do the same for others!

Please see #114335 for more context

Signed-off-by: Davanum Srinivas davanum@gmail.com

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

Please note that we're already in Test Freeze for the release-1.26 branch. This means every merged PR will be automatically fast-forwarded via the periodic ci-fast-forward job to the release branch of the upcoming v1.26.0 release.

Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Wed Dec 7 23:57:34 UTC 2022.

[k8s-ci-robot]

@dims: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[dims]

/kind bug

[dims]

/priority critical-urgent

[dims]

looks much better (1.26 and master references match)

[davanum@c889f3bd53ed 19:32] ~/go/src/k8s.io/kubernetes/staging/publishing ⟩ rg -i -e "destination: " -e "repository: kms"
rules.yaml
2:- destination: code-generator
33:- destination: apimachinery
65:- destination: api
115:- destination: client-go
201:- destination: component-base
275:- destination: component-helpers
349:- destination: kms
361:- destination: apiserver
373:    - repository: kms
445:    - repository: kms
451:- destination: kube-aggregator
465:    - repository: kms
559:    - repository: kms
564:- destination: sample-apiserver
578:    - repository: kms
697:    - repository: kms
707:- destination: sample-controller
822:- destination: apiextensions-apiserver
838:    - repository: kms
940:    - repository: kms
947:- destination: metrics
1033:- destination: cli-runtime
1107:- destination: sample-cli-plugin
1192:- destination: kube-proxy
1278:- destination: kubelet
1364:- destination: kube-scheduler
1450:- destination: controller-manager
1464:    - repository: kms
1546:    - repository: kms
1552:- destination: cloud-provider
1570:    - repository: kms
1672:    - repository: kms
1678:- destination: kube-controller-manager
1698:    - repository: kms
1810:    - repository: kms
1816:- destination: cluster-bootstrap
1878:- destination: csi-translation-lib
1940:- destination: mount-utils
1972:- destination: legacy-cloud-providers
1994:    - repository: kms
2126:    - repository: kms
2132:- destination: cri-api
2164:- destination: kubectl
2298:- destination: pod-security-admission
2312:    - repository: kms
2394:    - repository: kms
2400:- destination: dynamic-resource-allocation

[liggitt]

/lgtm

[palnabarun]

/lgtm

[nikhita]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, nikhita, palnabarun

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:

• staging/publishing/OWNERS [dims,nikhita]

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

[dims]

@kubernetes/release-team-leads @kubernetes/release-managers Since we really need the bot to work, we need to merge this for 1.26, applying milestone.

/milestone v1.26