Access Control
This guide has been reviewed and reformatted for Ruk-Com Cloud PaaS. Screens may vary slightly by platform version.
Click or tap a screenshot to view it at its original size.
Objective
This guide explains how to use Access Control on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.
Before you begin
- Sign in with an account permitted to manage the relevant environment.
- Confirm the target environment, region and resources before saving changes.
- Create a backup or rollback plan before changing a production system.
KubernetesManage access to the cluster viaRBAC(Role-Based Access Control) By default you will have a token that belongs toServiceAccountwith cluster-admin role
If you want to share access to your Kubernetes cluster with other users, it is recommended to create one.ServiceAccountsSeparately along withRoles and RoleBindingsWhere required, such steps help in managing manual authorization actions (e.g. to create namespaces, deployments, services, ingresses, etc.).
Note:
The Kubernetes RBAC system is not compliant with Ruk-Com accounts. Users with SSH access to the master node can use the kubectl tool pre-configured with cluster-admin role Because of this specific usage,environment sharingThrough Ruk-Com PaaS functionality, sensitive information may be exposed.