Skip to content

Allow a single Swarm per single team #114

Closed
@bohdan-shulha

Description

@bohdan-shulha

Currently there are no much filters over the dashboards and forms.

However, to separate the services we will introduce projects. With project may come namespaces or environments (not yet decided).

This way, each page/form will require to have, at least, 3 additional, and dependent on each other, filters.

To fight the complexity, it makes sense to limit the flexibility of the service.

Users should not be able to create multiple swarms per team.

This should also help with the separation of access roles for larger companies. Many will want to have a dedicated "staging" environment where "everyone" will be do everything and a "production" environment where only specific people would be able to make changes.

Separating these two into different swarms AND teams will simplify UI & UX by a lot.

As a side note, consider creating multiple swarm clusters per team as a feature for "business" plans only.

Metadata

Metadata

Assignees

No one assigned

    Labels

    cloudfeatNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions