Teaming in Kubera

Kubera is a complete solution to run and manage data on Kubernetes. Kubera provides you with GUI-based management and monitoring solution, pre-workload backup capabilities, enterprise build of OpenEBS(CNCF project), and whatnot. It has been developed by analyzing and addressing the needs of our customers. The basic features are FREE! Check it out, if you haven’t already.

What is teaming in Kubera?

So, you've signed up for Kubera, and you're wondering if you should share your credentials with the rest of the team. We've got you covered! With Kubera's Teaming feature, you can invite your teammates and assign them roles. Your teammates can log in with their own unique credentials and get to work on the same project.

The number of members that can be added to the project depends on your Kubera subscription plan.

What user roles are available for Kubera teammates?

The following roles can be designated to users, based on the functional requirements:

1. projectOwner: The project owner is the user who has created the project. Apart from normal configurational operations, the owner has some privileges. These have been listed below:

            Special Privileges:

  • Can invite other users to the project.
  • Can change the roles of the members in the project.
  • Can delete a member from the project.

           Configurational settings include:

  • Connecting or disconnecting clusters.
  • Enabling or disabling of application monitoring.
  • Performing backup and restore.
  • Performing OpenEBS upgrade, creation of storage pools, and other day-0 operations.
  • View and acknowledge alerts.
  • Configure alert rules.
  • Configuring chatops.
  • Viewing logs and graphs.
  • Make all "get" api requests.
2. projectAdmin: The projectAdmin can perform all the actions, excluding the special privileges given to the owner. The actions that they can perform include:
  • Connecting or disconnecting clusters.
  • Enabling or disabling of application monitoring.
  • Performing backup and restore.
  • Performing OpenEBS upgrade.
  • Managing alerts.
  • Configuring chatops.
  • Viewing and acknowledging alerts, graphs, and logs.
  • Make all "get" api requests.

3. projectReadAdmin: The projectReadAdmin can carry out all the operations to fetch information about the cluster, but cannot make any changes in the cluster. The actions that they can perform includes:

  • Viewing and acknowledging alerts, graphs, and logs.
  • Make all "get" api requests.

4. projectMember: The projectMember account is basically a restricted account. It does not have any access initially but can be granted access by the owner as per requirement.

Invite members to your project

The number of members that you can invite to your project depends on your subscription plan. A single user can be a part of multiple projects. To invite a user, log in to Kubera and go to Users and Roles.

Teaming in Kubera: fig 1

This displays all the users who have access to the project, pending invites(invites that have been sent and have not yet been approved), and details of each user connected to the project. To send an invite, click on Invite user and fill in the email ID and role that the user has to be assigned (The assigned roles can be edited afterward).

Note: Invitations can also be sent to users who are not using Kubera. On accepting the invitation, the invitee will be taken through steps for registering with Kubera.

Teaming in Kubera: fig 2

Accepting an invitation

1. For an existing Kubera user:

Click on your profile. This opens a drop-down menu displaying Invites as one of the options.

Teaming in Kubera: fig 3

Clicking on Invites redirects to a page that displays all the pending invites that you have received. Now, the invitation can either be accepted or rejected as per requirement.

2. For users not Signed Up to Kubera:
In such cases, the user will receive an email, which contains a link. Using this link, one can join Kubera. Joining Kubera using an invite adds you to the project and also creates a default project.

You can switch between your projects from the drop-down menu, as shown below.

Teaming in Kubera: fig 4

You will notice there is another project added by default named DemoDock. This is a demo project added to your account by default to understand the capabilities of Kubera. To know more about this project, click here.

Don Williams
Don is the CEO of MayaData and leading the company for last one year. He has an exceptional record of accomplishments leading technology teams for organizations ranging from private equity-backed start-ups to large, global corporations. He has deep experience in engineering, operations, and product development in highly technical and competitive marketplaces. His extensive professional network in several industries, large corporations and government agencies is a significant asset to early stage businesses, often essential to achieve product placement, growth and position for potential exit strategies.
Kiran Mova
Kiran evangelizes open culture and open-source execution models and is a lead maintainer and contributor to the OpenEBS project. Passionate about Kubernetes and Storage Orchestration. Contributor and Maintainer OpenEBS projects. Co-founder and Chief Architect at MayaData Inc.
Murat Karslioglu
VP @OpenEBS & @MayaData_Inc. Murat Karslioglu is a serial entrepreneur, technologist, and startup advisor with over 15 years of experience in storage, distributed systems, and enterprise hardware development. Prior to joining MayaData, Murat worked at Hewlett Packard Enterprise / 3PAR Storage in various advanced development projects including storage file stack performance optimization and the storage management stack for HPE’s Hyper-converged solution. Before joining HPE, Murat led virtualization and OpenStack integration projects within the Nexenta CTO Office. Murat holds a Bachelor’s Degree in Industrial Engineering from the Sakarya University, Turkey, as well as a number of IT certifications. When he is not in his lab, he loves to travel, advise startups, and spend time with his family. Lives to innovate! Opinions my own!