Support for Multiple Users with Private Apps and Groups

[guoguoguilai]

Description

Description

Hi, I would like to request a feature that supports multiple users, each of whom can have their own private apps deployed. Additionally, it would be great to have the ability to create groups where users can be added, allowing them to access the apps within that group.

Use Case

User Management: Each user can manage their own private applications.
Group Collaboration: Users can collaborate within groups, sharing access to specific apps.
Access Control: Administrators can control which users have access to which apps based on group membership.

Benefits

Enhanced collaboration among team members.
Improved organization of applications by grouping them.
Better access control and privacy for users' individual apps.

Possible solution

Proposed Implementation

User Accounts: Allow users to create individual accounts with private app deployment capabilities.
Group Creation: Implement a feature to create groups and manage group membership.
Access Management: Provide a way to set permissions for apps based on group membership.

Alternatives

No response

Additional information

No response

[mms-gianni]

I really like this idea and think this is something Kubero should have.

I'm not sure yet, how to implement it, since Kubero has no database to store these team/group informations. All entities are stored in etcd. So there should be a Kubernetes native way to achieve this. A configmap might be not dynamic enough.

this would some kind of "Teams" feature.

It may relay to RBAC issue here : #545

[mms-gianni]

I had another idea: It is possible to run multiple instances of the Kubero UI. Each instance only has access to its own pipelines. Each team would only see its own resources.

This would already be possible today.

[guoguoguilai]

I had another idea: It is possible to run multiple instances of the Kubero UI. Each instance only has access to its own pipelines. Each team would only see its own resources.

This would already be possible today.

Thanks for considering my feature request! I'm thrilled to see that you like the idea of introducing multi-user support with private app deployment and group collaboration features. I completely agree that this would be a great addition to Kubero, and I'm excited to see how it could enhance collaboration and organization for users.

Regarding the implementation, I understand the challenges of working with etcd and the need for a Kubernetes-native approach. I appreciate your willingness to explore solutions, and I'm happy to help brainstorm or provide input if needed.

The 'Teams' feature idea is intriguing. I also like your alternative idea of running multiple instances of the Kubero UI, each with access to its own pipelines and resources. This could be a viable workaround, and it's great that it's already possible today.

Thanks again for your time and consideration. I'm looking forward to seeing how this feature request evolves and potentially becomes a part of Kubero in the future!