Access Control in Kubernetes
To control access to the cluster, Kubernetes employs Role-Based Access Control (RBAC). You have a token included by default with a cluster-admin role-holding ServiceAccount.
It is recommended to build distinct ServiceAccounts for each user you wish to grant access to the Kubernetes cluster, together with the appropriate Roles and RoleBindings. With this method, you can manage the operations that each user can carry out, including namespace creation, deployments, services, and ingresses.
Notes:
- PaaS accounts are not integrated with the Kubernetes RBAC mechanism. With cluster-admin credentials, the pre-configured kubectl tool can be used by any user having SSH access to the master node. Accordingly, sharing the platform’s environments may reveal private information.
- Additionally, as Kubernetes dynamically maintains its own firewall rules, the platform’s firewall capability does not apply to the Kubernetes Cluster.
Save $100 in the next
5:00 minutes?