POC Permissions
The identity that runs install.sh needs these permissions. On a new cluster, a permission check confirms them before Terraform creates anything, and names any that is missing.
New cluster
-
AWS
-
Google Cloud
-
Azure
Permissions to create VPC, EC2, Elastic IP, IAM role, S3, and EKS resources. AdministratorAccess is the simplest; PowerUserAccess isn’t enough, because it can’t create IAM roles. The permission check confirms these actions:
| Service | Actions |
|---|---|
EC2 / VPC |
|
EKS |
|
IAM |
|
S3 |
|
The check itself |
|
Use the same AWS identity for Terraform and install.sh. EKS makes only the identity that created the cluster its admin.
These roles on the project, or roles/owner. Roles from your organization, a folder, or a group count.
| Role | Needed for |
|---|---|
|
Turning on the Compute Engine and Kubernetes Engine APIs |
|
The network, subnet, Cloud NAT, and static IP |
|
The GKE cluster, its nodes, and installing Kloudfuse |
|
The nodes' service account |
|
Running the nodes as that service account |
|
Giving that service account its roles |
|
The storage bucket and the nodes' access to it |
A project Owner can grant a role:
gcloud projects add-iam-policy-binding <project_id> \
--member="user:<you@example.com>" --role="roles/storage.admin" --condition=None
Owner on the subscription, or Contributor and User Access Administrator. Contributor creates the resources; User Access Administrator lets Terraform give the cluster’s identities access to the network, the public IP, and the storage account. Role Based Access Control Administrator also works if its condition allows assigning Network Contributor and Storage Blob Data Contributor. Roles through a group or a management group count.
A subscription Owner can grant a role:
az role assignment create --assignee <you@example.com> \
--role "User Access Administrator" --scope /subscriptions/<subscription_id>
If you are sure you have the permissions but the check reports some as missing (it can’t evaluate every organization policy), add skip_permission_check = true to terraform.tfvars and run ./install.sh again. A permission that really is missing then fails part-way through the install.
Existing cluster
Terraform isn’t used, so no cloud permissions are needed to create resources. You need:
-
A kubeconfig context with
cluster-admin, because the install creates CRDs, a storage class, and cluster roles. -
Access to the storage for the Kloudfuse node. On AWS, the node’s IAM role needs the S3 actions, and on Google Cloud the node’s service account needs the bucket roles, listed in Existing cluster requirements.
-
On Azure,
Network Contributorfor the cluster’s identity on the resource group of the static public IP.