Cloud Workstations

Related topics

• Cloud Workstations depends on Private Service Connect From the official documentation: “Your workstations connect to the control plane through Private Service Connect.”
• Artifact Registry works with Cloud Workstations From the official documentation: “To host custom container images, we recommend and support Artifact Registry. If you use GitHub or any other public or private repository, Cloud Workstations might not work as expected.”
• Cloud Workstations works with Shared VPC From the official documentation: “To enable Cloud Workstations to use your Shared VPC network and subnetwork, grant the Cloud Workstations Service Agent for your project the [Compute Engine Network User role](/compute/docs/access/iam#compute.networkUser) (`roles/compute.networkUser`) on the Shared VPC subnet.”
• Identity and Access Management secures Cloud Workstations From the official documentation: “Cloud Workstations uses Identity and Access Management (IAM) for authorization.”
• VPC Service Controls secures Cloud Workstations From the official documentation: “The API for Cloud Workstations can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
• Cloud Logging works with Cloud Workstations From the official documentation: “Cloud Logging receives, indexes, and stores platform log entries from Google Cloud services, such as Cloud Workstations.”
• Cloud Shell is an alternative to Cloud Workstations From the official documentation: “Upgrade from Cloud Shell to Cloud Workstations for managed secure development environments provisioned in your VPC.”
• Cloud Workstations depends on Compute Engine From the official documentation: “Workstations are hosted on Compute Engine instances.”
• Cloud Workstations works with Gemini Code Assist From the official documentation: “Gemini Code Assist is available by default in the following IDEs: - [Cloud Shell Editor](https://cloud.google.com/shell) - [Cloud Workstations](https://cloud.google.com/workstations)”
• Cloud Workstations works with Google Cloud CLI From the official documentation: “After you launch Cloud Workstations, you can access Google Cloud services and the API using your user accounts through the `gcloud` CLI.”
• Code OSS for Cloud Workstations is part of Cloud Workstations From the official documentation: “Cloud Workstations comes with a default base editor that lets you write, build, test, debug, and run your applications.”
• Terraform configures Cloud Workstations From the official documentation: “[Terraform](https://www.terraform.io/) is an infrastructure-as-code (IaC) tool that you can use to provision resources and permissions for Cloud Workstations.”
• BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Cloud Storage From the official documentation: “External BigQuery data source backed by Cloud Storage”
• Cloud Shell works with Google Cloud CLI From the official documentation: “Cloud Shell comes preinstalled with the [Google Cloud CLI](/sdk/gcloud) and Ruby.”
• BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• Identity and Access Management secures Cloud Service Mesh From the official documentation: “Access to Cloud Service Mesh in the Google Cloud console is controlled by [Identity and Access Management (IAM)](/iam/docs/overview).”
• Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
• Google Cloud CLI is part of Cloud Shell From the official documentation: “If you use Cloud Shell, Google Cloud CLI comes pre-installed.”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
• Cloud Logging works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh stores the dry-run results to Cloud Logging in the following labels:”
• Cloud Run works with Cloud Service Mesh From the official documentation: “This section shows you how to troubleshoot common errors with Cloud Service Mesh and Cloud Run.”
• Cloud Service Mesh works with VPC Service Controls From the official documentation: “You can now use VPC Service Controls with Cloud Service Mesh.”
• Cloud Shell is an alternative to Google Cloud CLI From the official documentation: “Open Cloud Shell or, if you installed the Google Cloud CLI on your local workstation, then open a terminal.”
• Cloud Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
• Cloud Run is an alternative to GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
• Shared VPC works with VPC Service Controls From the official documentation: “If you use both Shared VPC and VPC Service Controls, the host project that contains the network and the service project that contains the Managed Lustre instance must both be inside the same perimeter.”
• Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• Artifact Registry works with Cloud Run From the official documentation: “Cloud Run recommends using Artifact Registry.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Service Mesh depends on GKE From the official documentation: “Provision managed Cloud Service Mesh on a GKE cluster.”
• Cloud Service Mesh works with GKE From the official documentation: “# Set up a proxyless gRPC service mesh on GKE”
• Cloud Storage works with Google Cloud CLI From the official documentation: “The gcloud CLI is the preferred command line tool for accessing Cloud Storage.”
• Google Cloud CLI is an alternative to Terraform From the official documentation: “This section provides steps for creating the user cluster using the console, `gkectl`, Terraform, or the gcloud CLI.”
• Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• Artifact Registry works with Compute Engine From the official documentation: “Compute Engine can pull containers directly from Artifact Registry repositories.”
• Artifact Registry works with GKE From the official documentation: “In the next tutorial, you deploy those images from the Artifact Registry repository to a GKE cluster:”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• Cloud Service Mesh works with Compute Engine From the official documentation: “You can run applications on the following platforms and adopt them into a global service mesh that Cloud Service Mesh configures. | Feature | Supported | | --- | --- | | Compute Engine virtual machine (VM) instances | ✔ |”
• Cloud Service Mesh works with Identity and Access Management From the official documentation: “For information about how and which permissions are evaluated for each method, see the Identity and Access Management documentation for Cloud Service Mesh.”
• Cloud Service Mesh works with Shared VPC From the official documentation: “For a detailed explanation of how Shared VPC is supported with Cloud Service Mesh, see [Limitations](/service-mesh/v1.25/docs/service-routing/limitations).”
• Cloud Storage works with Compute Engine From the official documentation: “You can use a web browser, the Google Cloud CLI, or a programming language to transfer files between Cloud Storage and Compute Engine VMs.”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• Private Service Connect works with VPC Service Controls From the official documentation: “VPC Service Controls that use Private Service Connect”
• VPC Service Controls secures Artifact Registry From the official documentation: “If your VPC Service Controls settings are blocking access to Artifact Registry, you must add the Artifact Registry service to the service perimeter of your VPC Service Controls.”
• Artifact Registry works with Google Cloud CLI From the official documentation: “Before you can push or pull images, configure Docker to use the Google Cloud CLI to authenticate requests to Artifact Registry.”
• BigQuery works with Cloud Run From the official documentation: “You can then use Cloud Run to transcode data present in the bucket and move it to BigQuery.”
• BigQuery works with Gemini Code Assist From the official documentation: “Gemini Code Assist fetches and uses relevant BigQuery and Dataproc Metastore tables and their schemas to generate a code response.”
• Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
• Cloud Logging works with Dataflow From the official documentation: “Information stored in [Cloud Logging](/logging/docs/region-support) is primarily generated by the code in your Dataflow program.”
• Cloud Logging works with Gemini Code Assist From the official documentation: “If required, you can set up Gemini Code Assist Standard and Enterprise to store user input and responses in a Cloud Logging bucket.”
• Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
• Cloud Run works with Identity and Access Management From the official documentation: “Cloud Run also offers the ability to control access to a service with Identity and Access Management (IAM).”