Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Organization-based VM Access Filtering #1395

Open
sergio-garciagil opened this issue Apr 30, 2024 · 2 comments
Open

Organization-based VM Access Filtering #1395

sergio-garciagil opened this issue Apr 30, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@sergio-garciagil
Copy link

As an SRE responsible for managing multiple organizations across different clients within Google Cloud Platform.

Proposed Solution:
Introducing a new feature that enables access filtering based on organizations. This feature could be implemented as follows:

Add a dropdown menu within the access control settings, labeled "Organization Filter".
By default, the dropdown would display "All", allowing unrestricted access to VMs across all organizations.
Users would have the option to select a specific organization
Upon selecting a particular organization, IAPDesktop would only display VMs associated with projects within that organization

@jpassing
Copy link
Collaborator

If I understand correctly, you're looking for a better visual separation between projects from different organizations. If that's correct, I figure adding an extra "level" in the tree structure might work as well? Something like:

+ Cloud
   + example.com                  <--- new level
       + project-1
          + us-east1-a
          ...
       + project-1
       ...
   + another-org.example
       + project-3
       + project-4
       ...

One limiting factor is that looking up the organization requires the Organization Viewer role, and not everybody has that role. In that case, we'd have to group projects under a pseudo node such as Unknown organization.

Of course, there's also the option to have separate profiles and you could maintain one profile per client. That's more heavyweight, but it also (optionally) allows you to use different user accounts. Is that something you have considered?

@jpassing jpassing added the enhancement New feature or request label Apr 30, 2024
@sergio-garciagil
Copy link
Author

It's exactly like what you draw in your diagram! You're right about the role; in my case, I do have it. We also thought about different profiles, but in my case, I manage more than 20 organizations, so the process would be quite complex and tedious.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants