IssueTracker

This will create a public issue which anybody can view and comment on.

Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.

Problem you have encountered:

• The customer needs to configure some easy to read URLs for their Dataproc components

What you expected to happen:

• An out-of-the-box tool to generate a custom URL token to access the different Dataproc components. These new URLs would also need to have an Auth token in some way due to the fact that the components use Identity-Aware Proxy.

Other information (workarounds you have tried, documentation consulted, etc):

• There are already options to create URLs for these components using the master-host-name as a base [1]. There is also an option to create the URL using the component-gateway-base-url and component path as a base [2]
• Another possible workaround could be to set a custom DNS to redirect the custom URL to the one that already exists. The main issue with this alternative is that there would need to be some way to authenticate the custom URL every time they use it since the component URL can only be accessed via an Identity-Aware Proxy.

[1]https://cloud.google.com/dataproc/docs/concepts/accessing/cluster-web-interfaces [2]https://cloud.google.com/dataproc/docs/concepts/accessing/dataproc-gateways