Ruk-Com PaaS Documentation

Build, deploy and operate applications on the platform.

RUK-COM PAAS / KUBERNETES HOSTING

Access Control

This guide is maintained for Ruk-Com PaaS. Screens and options may vary by platform version and account permissions.

Confirm the environment, region and account permissions, and back up current settings before changing a production system.

Kubernetes manages access to the cluster via RBAC (Role-Based Access Control). By default, you have a token that belongs to a ServiceAccount with the cluster-admin role.

If you need to share access to the Kubernetes cluster with other users, it is recommended to create separate ServiceAccounts with the required Roles and RoleBindings. Such a flow helps to manage allowed actions manually (e.g., to create namespaces, deployments, services, ingresses, etc.).

Notes:

  • Kubernetes RBAC system is not aligned with PaaS accounts. Any user with SSH access to the master node can utilize the pre-configured kubectl tool with its cluster-admin role. Due to this specific, environment sharing over the platform functionality may expose sensitive information.
  • The platform firewall feature does not work with the Kubernetes Cluster, as the rules are managed dynamically by Kubernetes itself.