IssueTracker

This will create a feature request which anybody can view and comment on.

Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.

What you would like to accomplish:

Per [GCP documentation](https://cloud.google.com/vpc-service-controls/docs/supported-method-restrictions), the Dataproc API doesn't support method-level ingress and egress rules for VPC-SC perimeters. Currently, restricting the Dataproc API in a VPC-SC perimeter stops me from connecting to a Jupyter notebook running on that cluster, meaning I can't allow notebook access while restricting other parts of the API.


How this might work:

Supporting method-level ingress and egress rules like other APIs would allow me to enable notebook access while disabling other portions of the API.

If applicable, reasons why alternative solutions are not sufficient:

My current workaround is not restricting the Dataproc API in the perimeter at all. However, this exposes the entire API instead of just allowing users to connect to existing notebooks.