Assigned
Status Update
Comments
ba...@google.com <ba...@google.com>
ma...@google.com <ma...@google.com> #2
Hello,
Thanks for reaching out to us!
The Product Engineering Team has been made aware of your Issue request, and will address it in due course. Though we can't provide an ETA on Issue requests nor guarantee their implementation, rest assured that your feedback is always taken very seriously, as it allows us to improve our products. Thank you for your trust and continued support to improve Google Cloud Platform products.
In case you want to report a new issue, please do not hesitate to create a new
Thanks and Regards,
Mahaboob Subhani
Google Cloud Support
Description
Cloud Storage, Compute and Container API are all protected by the same perimeter and all the resources in question (GKE Node and GCS Bucket) are within the same project. So, a VPC SC violation should not have happened.
But an Ingress violation happens with source and targetResource being the same.
This is due to inconsistent enforcement when adding projects to a perimeter and this is a known issue internally.
Raising this Public Issue Tracker so that the customers can track this issue and they can be aware of the further updates.