Teams and Resource Groups: Improving Collaboration in Testkube

At Testkube - we build a platform which helps people test their Cloud-native application at scale. We strive to create a product that is efficient, secure, and tailored to meet the needs of growing teams. Today, we are excited to announce the release of new functionality that helps teams collaborate safely in complex testing environments—across multiple teams which share the same resources and infrastructure. 

The Challenge: Managing Resources Across Teams in Shared Environments

Separate teams often need to run tests against their respective components in a cloud-native application, while leveraging the same underlying infrastructure for test execution. In more mature organizations, depending on a team, a portion of an application or an Environment (Dev, Staging, Prod), different teams require different sets of permissions. These types of challenges require teams to collaborate in a more organized fashion, with defined rules, permissions, and guardrails.

For example, a Dev team may not be allowed to run Load tests against a Production environment. Not that some developers don’t like to test in production :).  A Front-End team should be able to run Playwright or Cypress tests but not Postman API tests.

Our Solution: Introducing Teams and Resource Groups

To solve these challenges, we have added both Teams and Resource Groups to provide a clear framework for organizing users and their access to Testkube resources (Workflows, Triggers, Templates, etc). These enhancements build upon the existing Role-Based Access Control (RBAC) functionality for Testkube Environments, adding more granularity and flexibility to control access and manage collaboration in large organizations.

Key Features of Teams and Resource Groups:

1. Team-Based Access Management:

Users can be grouped into Teams. These teams can be added to both existing Testkube Environments and assigned to specific groups of resources across all Environments - Resource Groups Groups. 

2. Resource Groups with Role Assignments:

Resource Groups allow you to group Testkube Resources across your environments into logical units, for example by component, team or release. Teams and users can be assigned to Resource Groups with a specific role (Read, Run, Write, Admin). Users and teams can hold only one role per Resource Group, simplifying the structure and reducing confusion.

3. Enhanced Resource Organization:

By assigning resources such as your Test Workflows to Resource Groups, users only work with the Testkube resources they have access to across all Testkube Environments, making it easy for teams and their members to focus on their testing activities without interfering with those of other teams. This helps streamline collaboration and ensures that teams can work within well-defined boundaries.

Start Using Testkube as a Team

Start using Teams and Access Groups today to take control of your testing environment! We believe this feature will significantly improve team management and resource access in shared Kubernetes environments. For new users, get started today with a free trial of either SaaS or On Prem. For existing customers, follow the instructions to upgrade. For enterprise users running Testkube in air gapped environments, please contact us for help upgrading.

This feature is built with collaboration in mind, and your feedback is crucial to ensuring it meets your needs. Please feel free to reach out to me directly at bruno@kubeshop.io, or connect with our community on Slack for any questions or suggestions.

Thank you for your continued trust in Testkube.