Set up Project

Creating a Google Cloud project for your Kubeflow deployment

In order to create GKE cluster and deploy Kubeflow on it, you need to set up a Google Cloud project and enable necessary APIs for the deployment.

Set up project and API scopes

Follow these steps to set up your Google Cloud project:

  • Select or create a project on the Google Cloud Console. If you plan to use different Google Cloud projects for Management Cluster and Kubeflow Clusters: create one Management project for Management Cluster, and create one or more Kubeflow projects for Kubeflow Clusters.

  • Make sure that you have the Owner role for the project in Cloud IAM (Identity and Access Management). The deployment process creates various service accounts with appropriate roles in order to enable seamless integration with Google Cloud services. This process requires that you have the owner role for the project in order to deploy Kubeflow.

  • Make sure that billing is enabled for your project. Refer to Enable billing for a project.

  • Open following pages on the Google Cloud Console and ensure that the specified APIs are enabled for all projects:

    You can also enable these APIs by running the following command in Cloud Shell:

    gcloud services enable \ \ \ \ \ \ \ \ \ \ \ \ \
    # Cloud Build API is optional, you need it if using Fairing.
    # gcloud services enable
  • If you are using the Google Cloud Free Program or the 12-month trial period with $300 credit, note that the free tier does not offer enough resources for default full Kubeflow installation. You need to upgrade to a paid account.

    For more information, see the following issues:

    Read the Google Cloud Resource quotas to understand quotas on resource usage that Compute Engine enforces, and to learn how to check and increase your quotas.

  • Initialize your project to prepare it for Anthos Service Mesh installation:

    curl --request POST \
      --header "Authorization: Bearer $(gcloud auth print-access-token)" \
      --data '' \${PROJECT_ID}:initialize

    Refer to Anthos Service Mesh documentation for details.

    If you encounter a Workload Identity Pool does not exist error, refer to the following issue:

    • kubeflow/website #2121 describes that creating and then removing a temporary Kubernetes cluster may be needed for projects that haven’t had a cluster set up beforehand.

You do not need a running GKE cluster. The deployment process creates a cluster for you.

Next steps


Was this page helpful?

Last modified September 8, 2022: Cherry-pick GKE updates (#3356) (c9bcb6b1)