Add rbac permissions for networking.gke.io/frontendconfigs

[spencerhance]

This will need to be cherry-picked into release-1.9 asap

Tested the rbac config in a sandbox

[k8s-ci-robot]

Hi @spencerhance. 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/test-infra repository.

[spencerhance]

/assign @freehan

[bowei]

is there an e2e test? How do we catch this next time?

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bowei, spencerhance

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:

• OWNERS [bowei]

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

[spencerhance]

Thanks @bowei! Any e2e test using a new CRD will catch this in a real cluster. The issue is that you won't see this if you run the binary locally (--running-in-cluster=false).

As far as catching this earlier, I'm not sure what else to do besides potentially writing a quick guide for adding new CRDs.