VK Cloud logo

Access management

To differentiate permissions for invited members of a project or service accounts, Managed Containers uses a unified identity and access management service — IAM. Access can be managed centrally from the VK Cloud personal dashboard.

The list of actions available to a project member in the Managed Containers service is determined by:

  • Basic role — defines user permissions at the level of all VK Cloud services.
  • Specialized role — defines user permissions at the level of individual VK Cloud services.

Configuring individual permissions for Managed Containers is not supported.

Roles can be assigned only by project members with the Project Owner, Superadministrator, and User Administrator (IAM) roles. When choosing roles, follow the principle of least privilege: a user should have only the permissions without which their tasks cannot be performed.

Basic roles

The basic roles Project Owner, Superadministrator, and Project Administrator grant full access to all Managed Containers operations; there is no need to configure individual roles.

mcs_owner

Name in the management console: Project owner.

The role with the maximum set of permissions in the project. The role is automatically assigned to the user who created the project themselves, or for whom the project was automatically created upon account registration.

A project can have only one owner. This role cannot be assigned manually or invited to.

mcs_co_owner

Name in the management console: Super administrator.

A role that grants permissions to manage all project resources. This role can only be assigned to a user by the project owner.

mcs_admin

Name in the management console: Project administrator.

A role that grants permissions to manage all project resources except user groups and the balance.

mcs_admin_security

Name in the management console: User administrator (IAM).

A role designed for managing project members on the access management page. The user administrator can invite members to the project and remove them from it, and edit the roles assigned to members. Services and project balance information are not available for this role.

In the Cloud Logging service, the role allows viewing logs.

In the Cloud Monitoring service, the role allows viewing dashboards.

In the Cloud Audit service, the role allows viewing IAM service events and the user's own actions.

mcs_viewer

Name in the management console: Observer.

A role that grants permissions to view most of the information about the project and resources, but does not have permissions to create or modify them.

In the Cloud Logging service, the role allows viewing logs.

In the Cloud Monitoring service, the role allows viewing dashboards.

In the Cloud Audit service, the role allows viewing all project events and exporting this data.

In the Managed Containers service, the role allows viewing information about the cluster and node groups and obtaining a secret for access to Headlamp.

Specialized roles

For the Managed Containers service, several specialized roles are available that can be used together with a basic role or on their own.

mcs_k8s_viewer

Name in the management console: Kubernetes auditor.

A role with permissions to view the Managed Containers service.

A user with this role can:

  • view information about the cluster and node groups;
  • obtain the kubeconfig file;
  • obtain a secret for access to the Kubernetes Dashboard.

In the Cloud Logging service, the role allows viewing logs and generating credentials.

In the Cloud Monitoring service, the role allows viewing, creating, and editing dashboards, as well as writing to the monitoring system.

In the Cloud Audit service, the role allows viewing Managed Containers service events and the user's own actions, as well as exporting this data.

mcs_k8s_editor

Name in the management console: Kubernetes operator.

A role with permissions for working in the Managed Containers service. Some actions are only available in a specific cluster state. For example, installing and removing add-ons is only possible if the cluster is running.

A user with this role can:

  • start and stop clusters;
  • display information about the cluster and node groups;
  • obtain the kubeconfig file;
  • obtain a secret for access to the Kubernetes Dashboard;
  • update the cluster version;
  • change the virtual machine type;
  • change the size of the Prometheus disk;
  • add or remove a node group;
  • change the scaling settings of node groups;
  • change labels and taints;
  • install or remove add-ons.

In the Cloud Logging service, the role allows viewing logs and generating credentials.

In the Cloud Monitoring service, the role allows viewing, creating, and editing dashboards, as well as writing to the monitoring system.

In the Cloud Audit service, the role allows viewing Managed Containers service events and the user's own actions, as well as exporting this data.

mcs_k8s_admin

Name in the management console: Kubernetes administrator.

A role with the broadest set of permissions for working with the Managed Containers service. Some actions are only available in a specific cluster state. For example, installing and removing add-ons is only possible if the cluster is running.

A user with this role can:

  • create and delete clusters;
  • start and stop clusters;
  • display information about the cluster and node groups;
  • obtain the kubeconfig file;
  • obtain a secret for access to the Kubernetes Dashboard;
  • update the cluster version;
  • change the virtual machine type;
  • change the size of the Prometheus disk;
  • add or remove a node group;
  • change the scaling settings of node groups;
  • change labels and taints;
  • install or remove add-ons.

In the Cloud Logging service, the role allows viewing logs and generating credentials.

In the Cloud Monitoring service, the role allows viewing, creating, and editing dashboards, as well as writing to the monitoring system.

In the Cloud Audit service, the role allows viewing Managed Containers service events and the user's own actions, as well as exporting this data.

Relationship between personal dashboard roles and Kubernetes

A user authenticates in a Kubernetes cluster with the same credentials as when logging in to the VK Cloud personal dashboard, using Single Sign-On (SSO) technology. Each specialized role — Kubernetes administrator, operator, or auditor — also determines the internal Kubernetes role available to the user. The Kubernetes role determines which cluster objects are available to the user and which actions are allowed to be performed on those objects.

To view the list of resources available for a role, connect to the cluster and run the command:

kubectl describe clusterrole <KUBERNETES_ROLE>

Kubernetes role: view.

The role provides read access to most objects in a namespace.

The role does not provide:

  • Access to view or modify roles and role bindings.

  • Access to secrets.

    A user with access to secrets can obtain the credentials of any service account in a namespace. This would allow access to the API on behalf of any service account in the namespace. For a role with read-only permissions, this would be considered a privilege escalation.

Was this article helpful?