blueprint

Related topics

• module is part of blueprint From the official documentation: “A *blueprint* is a package of deployable and reusable modules, and a policy that implements and documents a specific solution.”
• blueprint configures cluster From the official documentation: “To make basic configuration changes to a running cluster, it is recommended to edit and redeploy the blueprint.”
• blueprint works with Cluster Toolkit From the official documentation: “Cluster blueprints are YAML files that define reusable configurations for deploying high performance computing (HPC), artificial intelligence (AI), and machine learning (ML) workloads with Cluster Toolkit.”
• blueprint configures GKE From the official documentation: “You can make basic configuration changes to your deployed Google Kubernetes Engine (GKE) resources by editing and redeploying the associated blueprint.”
• blueprint is part of repository From the official documentation: “This repository will contain a blueprint (packaged Terraform files) describing how to provision your units.”
• policy is part of blueprint From the official documentation: “A blueprint is a package of deployable, reusable modules and policy that implements and documents a specific opinionated solution.”
• Cloud Service Mesh works with GKE From the official documentation: “# Set up a proxyless gRPC service mesh on GKE”
• Compute Engine is an alternative to GKE From the official documentation: “You can also deploy a third-party model to either Vertex AI Model Garden or self-host on GKE or Compute Engine.”
• Cloud Service Mesh depends on GKE From the official documentation: “Provision managed Cloud Service Mesh on a GKE cluster.”
• Cluster Toolkit works with GKE From the official documentation: “You can deploy GKE clusters by using GKE directly or by using Cluster Toolkit.”
• Binary Authorization works with GKE From the official documentation: “Now, you create a GKE cluster with Binary Authorization enabled.”
• Compute Engine works with Google Cloud CLI From the official documentation: “Some applications might use commands from the gcloud CLI, which is included by default in most Compute Engine images.”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• Binary Authorization secures Cloud Service Mesh From the official documentation: “[Google Cloud Binary Authorization](/binary-authorization) ensures that the workload images in the mesh are the ones authorized by the administrators.”
• Cloud Service Mesh works with Compute Engine From the official documentation: “Cloud Service Mesh supports a variety of infrastructures (GKE/Kubernetes, Compute Engine) and environments (on-premises, other clouds).”
• cluster works with Google Cloud CLI From the official documentation: “You can restore your backup to a new AlloyDB cluster using the Google Cloud console or Google Cloud CLI.”
• Cluster Toolkit is an alternative to Google Cloud CLI From the official documentation: “On this page, you learn how to create a GKE cluster with the Google Cloud CLI for maximum flexibility in configuring your cluster based on the needs of your workload. Alternatively, you can choose to use Cluster Toolkit to quickly deploy your cluster with default settings that…”
• customer-managed encryption keys secures Compute Engine From the official documentation: “In IL5, CMEK is enabled by default for Compute Engine, Google Kubernetes Engine (GKE), Cloud Storage, and Cloud SQL.”
• customer-managed encryption keys secures GKE From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
• GKE works with Google Cloud CLI From the official documentation: “GKE manages end-user authentication for you through the Google Cloud CLI.”
• kubectl is part of Google Cloud CLI From the official documentation: “The `gcloud` and `kubectl` tools are part of the Google Cloud CLI.”
• Binary Authorization works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh users need to only set up the Binary Authorization policy.”
• Binary Authorization secures GKE From the official documentation: “Use Binary Authorization to make sure trusted images are deployed to Google Kubernetes Engine (GKE) and Cloud Run.”
• Cloud Service Mesh is part of cluster From the official documentation: “- **Canary cluster migration**: In this strategy, you create a new cluster and then provision managed Cloud Service Mesh on it.”
• cluster works with GKE From the official documentation: “GKE is a container orchestration platform that works by connecting VMs into a *cluster*.”
• Cluster Toolkit configures GKE From the official documentation: “Use the [`gcluster deploy` command](/cluster-toolkit/docs/reference/gcluster-deploy) to deploy the blueprint and provision the GKE infrastructure using A3 Mega machine types:”
• Cluster Toolkit is an alternative to kubectl From the official documentation: “You can apply the manifests by using `kubectl` or [Cluster Toolkit](/cluster-toolkit/docs/overview).”
• Compute Engine is part of cluster From the official documentation: “Deleting the cluster deletes all the resources that make up the cluster, such as the Compute Engine instances, disks, and network resources.”
• customer-managed encryption keys secures cluster From the official documentation: “If you enable CMEK on a cluster, then AlloyDB uses your key to encrypt all of your cluster's data in storage.”
• customer-managed encryption keys secures repository From the official documentation: “All repository content is encrypted using either Google-owned and Google-managed encryption keys or customer-managed encryption keys.”
• GKE works with kubectl From the official documentation: “After the cluster is created, use the `kubectl` command-line tool, which is integrated with the [gcloud CLI](/sdk/gcloud), to interact with your GKE cluster.”
• Google Cloud CLI configures cluster From the official documentation: “The gcloud CLI and Terraform only support updating admin and user clusters.”
• Google Cloud CLI configures Compute Engine From the official documentation: “To replace a BYOL license with a PAYG license, use the Google Cloud CLI or the Compute Engine API.”
• kubectl configures cluster From the official documentation: “To update other custom resources that affect the cluster, you must use `kubectl` or `bmctl`.”
• policy is part of Binary Authorization From the official documentation: “2. Configure the default [rule](/binary-authorization/docs/key-concepts#rules) of your Binary Authorization [policy](/binary-authorization/docs/key-concepts#policies) to require attestations.”