Permissions listed here are permission required by the Kubermatic machine-controller. Terraform, and components deployed by KubeOne (such as external cloud-controller-manager) might require additional permissions.
For the access to the Compute Engine API it has to be enabled at the Google APIs console.
The user for the Google Service Account that has to be created has to have three roles:
gcloud CLI is installed, a service account can be created like follow:
# create new service account gcloud iam service-accounts create k8c-cluster-provisioner # get your service account id gcloud iam service-accounts list # get your project id gcloud projects list # create policy binding gcloud projects add-iam-policy-binding YOUR_PROJECT_ID --member 'serviceAccount:YOUR_SERVICE_ACCOUNT_ID' --role='roles/compute.admin' gcloud projects add-iam-policy-binding YOUR_PROJECT_ID --member 'serviceAccount:YOUR_SERVICE_ACCOUNT_ID' --role='roles/iam.serviceAccountUser' gcloud projects add-iam-policy-binding YOUR_PROJECT_ID --member 'serviceAccount:YOUR_SERVICE_ACCOUNT_ID' --role='roles/viewer'
A Google Service Account for the platform has to be created, see Creating and managing service accounts. The result is a JSON file containing the fields
The private key is BASE64 containing the newlines as non-escaped strings "\n". So to avoid the resulting troubles the machine controller expects the whole service account encoded in BASE64.
# create a new json key for your service account gcloud iam service-accounts keys create --iam-account YOUR_SERVICE_ACCOUNT k8c-cluster-provisioner-sa-key.json # create base64 encoded secret base64 -w 0 ./k8c-cluster-provisioner-sa-key.json
The base64 encoded secret of the service account will passed in the field
serviceAccount of the
cloudProviderSpec of the machine deployment.