aggregate-to-view RBAC for gmsacredentialspecs

[avin3sh]

gmsacredentialspecs doesn't contain anything sensitive and to ease cluster management we should include aggregate-to-view RBAC for gmsacredentialspecs.

Happy to send across a PR if there is an agreement.

[jsturtevant]

This seems fine to me. @aravindhp @marosset thoughts?

[jsturtevant]

https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles

[marosset]

it could expose some inforamtion aroudn the layout of the network (which dns name, SID, etc). I don't think this is sensitive but could be used to craft other attacks.
I'm indifferent as to if we should expose this or not

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[avin3sh]

I will send a PR

/remove-lifecycle stale