Cannot deploy Kubeflow on GCP: tells me to enable APIs that are already enabled

4/6/2020

I am trying to install Kubeflow on Google Cloud Platform (GCP) and Kubernetes Engine (GKE), following the GCP deployment guide.

I created a GCP project of which I am the owner, I enabled billing, set up OAuth credentials and enabled the following APIs:

  • Compute Engine API
  • Kubernetes Engine API
  • Identity and Access Management (IAM) API
  • Deployment Manager API
  • Cloud Resource Manager API
  • Cloud Filestore API
  • AI Platform Training & Prediction API

However, when I want to deploy Kubeflow using the UI, I get the following error:

enter image description here

So I doublechecked and those APIs are already enabled:

enter image description here

enter image description here

The log messages at the bottom of the screen are:

2020-03-0614:14:04.629: Getting enabled services for project <projectname>..
2020-03-0614:14:16.909: Could not configure communication with GCP, exiting

The Could not configure communication with GCP, exiting is triggered when _enableGcpServices() fails.

The line Getting enabled services for project ... is printed but not the line Proceeding with project number: ..., so the error must be triggered somewhere in the block of code between those lines.

The call to Gapi.cloudresourcemanager.getProjectNumber(project) has its own try/catch with a slightly different error message and title (only talks about the cloud resource manager API, not the IAM API), so I assume it is the call to Gapi.getSignedInEmail() that fails??

-- BioGeek
google-cloud-platform
kubeflow
kubernetes

2 Answers

4/29/2020

I faced the same issue and was able to solve by correcting the project id.

Make sure that the project id on the UI form is specified correctly as it is on the GCP project - and that it does not have any leading or trailing spaces if you copy pasted from the GCP project details like I did.

-- rakidedigama
Source: StackOverflow

4/6/2020

I'd suggest having a look at the service management API, IAM service credentials API and cloud identity aware proxy API possibly. I've only used the CLI install tool previously and not run into these problems, but you might require these services for the IAP deployment?

-- Joe Peskett
Source: StackOverflow