Update comment on ResourcePolicyRule

[MikeSpreitzer]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

This PR updates the comment on ResourcePolicyRule to account for the ClusterScope field, which was added long ago.

Which issue(s) this PR fixes:

Fixes #105393

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.:

[MikeSpreitzer]

@kubernetes/sig-api-machinery-api-reviews
/cc @tkashem
/cc @lavalamp
/cc @deads2k
/cc @wojtek-t

[k8s-triage-robot]

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

[MikeSpreitzer]

/test pull-kubernetes-integration

[MikeSpreitzer]

I am mystified about the generated swagger. pull-kubernetes-verify says

/home/prow/go/src/k8s.io/kubernetes/api/openapi-spec is out of date. Please run hack/update-openapi-spec.sh

But when I do that, it makes no difference.

mspreitz@ubu20:~/go/src/k8s.io/kubernetes$ git status
On branch fix-105393
Your branch is up to date with 'origin/fix-105393'.

nothing to commit, working tree clean
mspreitz@ubu20:~/go/src/k8s.io/kubernetes$ hack/update-openapi-spec.sh
make: Entering directory '/home/mspreitz/go/src/k8s.io/kubernetes'
make[1]: Entering directory '/home/mspreitz/go/src/k8s.io/kubernetes'
Generating prerelease lifecycle code for 3 targets
Generating deepcopy code for 3 targets
Generating defaulter code for 3 targets
Generating conversion code for 3 targets
Generating openapi code for KUBE
make[1]: Leaving directory '/home/mspreitz/go/src/k8s.io/kubernetes'
+++ [1008 00:55:56] Building go targets for linux/amd64:
    cmd/kube-apiserver
> static build CGO_ENABLED=0: k8s.io/kubernetes/cmd/kube-apiserver
make: Leaving directory '/home/mspreitz/go/src/k8s.io/kubernetes'
etcd --advertise-client-urls http://127.0.0.1:2379 --data-dir /tmp/tmp.pSNEa25XtY --listen-client-urls http://127.0.0.1:2379 --log-level=debug > "/dev/null" 2>/dev/null
Waiting for etcd to come up.
+++ [1008 00:56:18] On try 2, etcd: : {"health":"true","reason":""}
{"header":{"cluster_id":"14841639068965178418","member_id":"10276657743932975437","revision":"2","raft_term":"2"}}+++ [1008 00:56:18] Starting kube-apiserver
+++ [1008 00:56:23] On try 5, apiserver: : ok
+++ [1008 00:56:23] Updating 
    hack/../api/openapi-spec
+++ [1008 00:56:23] SUCCESS
+++ [1008 00:57:23] Clean up complete
mspreitz@ubu20:~/go/src/k8s.io/kubernetes$ 
mspreitz@ubu20:~/go/src/k8s.io/kubernetes$ git status
On branch fix-105393
Your branch is up to date with 'origin/fix-105393'.

nothing to commit, working tree clean

[liggitt]

Rebase on latest master and make clean… it looks like you have alpha types/serving code still in your branch or binaries

[MikeSpreitzer]

@liggitt : thanks, the make clean seems to have made the difference. I do not understand why that should be so.

[fedebongio]

/triage accepted

[MikeSpreitzer]

@fedebongio , @liggitt : what needs to happen for this to make progress?

[liggitt]

missed this was ready

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: liggitt, MikeSpreitzer

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:

• api/OWNERS [liggitt]
• staging/src/k8s.io/api/OWNERS [liggitt]

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