Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Permissions on GKE cluster

After creation of a standard GKE cluster in the Google Cloud Platform Console I find when I click on the cluster and look at the clusters' setting s a 'Permissions' setting, which looks like this: enter image description here

what I don't understand is that I have allowed API access on a lot of these service I believe, so why does only 'Cloud Platform' show 'enabled'? Is this what is enabled at creation of the cluster maybe?!

When selecting 'edit' you can not 'enable' these services from here..., so what exactly are these Permissions?

like image 426
musicformellons Avatar asked Jan 11 '19 11:01

musicformellons


People also ask

How do I give access to Gke cluster?

To enable access to your user clusters using the GKE console, complete the following steps: Create a node-reader. yaml file that allows you to access the cluster. Apply this file to the cluster that you want to log into with the kubectl command.

What is RBAC in GKE?

By default, no other users have access to your project or its resources, including Google Kubernetes Engine (GKE) resources. GKE supports multiple options for managing access to resources within your project and its clusters using role-based access control (RBAC). Identity and Access Management (IAM)


1 Answers

The GKE cluster will be created with the permissions that is set on the 'Access scopes' section in the 'Advanced edit' tab. So only the APIs with the access enabled in this section will be shown as enabled. These permissions denote the type and level of API access granted to the VM in the node pool. Scopes inform the access level your cluster nodes will have to specific GCP services as a whole. Please see this link for more information about accesss scopes.

In the tab of 'Create a Kubernetes cluster', click 'Advanced edit'. Then you will see another tab called 'Edit node pool' pops up with more options. If you click 'Set access for each API', you will see the option to set these permissions.

'Permissions' are defined when the cluster is created. You can not edit it directly on the cluster after the creation. You may want to create a new cluster with appropriate permissions or create a new Node Pool with the new scopes you need and then delete your old 'default' Node Pool as specified in this link .

like image 176
John Mathew Avatar answered Sep 29 '22 05:09

John Mathew