Assigned
Status Update
Comments
ah...@quantexa.com <ah...@quantexa.com>
va...@google.com <va...@google.com> #2
Hi , Could you please clarify the issue description or share any screen shot of the problem where you are facing issue ?
ah...@quantexa.com <ah...@quantexa.com> #3
Hi, its a feature request. Can you change it to feature request?
I am requesting a dataproc image version that supports spark 3.4
https://cloud.google.com/dataproc/docs/concepts/versioning/dataproc-release-2.2
I am requesting a dataproc image version that supports spark 3.4
va...@google.com <va...@google.com> #4
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the feature request
, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
ah...@quantexa.com <ah...@quantexa.com> #5
Hi,
Is there an update on the above? we want to know if device check is supported by dataproc components GW, if not, is there any plan to make it available please ?
Thanks Ahmed
Description
Problem you have encountered:
I have a dataproc cluster inside a VPC service control perimeter. I would like to allow access to the dataproc components gateway with access level and device policy check enabled. Example:
Access Level Settings:
Perimeter
I have then added the above access level to be used in the parameter but I get 401 error like the one in the screenshot attached.
What you expected to happen:
I expect the request to comply with the constraint and make a successful connection. p.s. the same access level is used elsewhere to validate connections with device policy check enabled.