Verifique se você tem permissões adequadas no projeto do Google Cloud
para atender aos requisitos de instalação do cluster,
da frota e do Cloud Service Mesh:
Se você tiver a função Proprietário em
projeto do Google Cloud, então você tem mais do que as permissões necessárias para
criar clusters, instalar e configurar o Knative serving.
Para saber como registrar seu cluster e ativar a Federação de Identidade da Carga de Trabalho para GKE na sua frota, consulte Como registrar um cluster. Os tipos de cluster com suporte fora do Google Cloud são registrados por padrão.
O Cloud Service Mesh requer que o cluster use um tipo de máquina com
pelo menos quatro vCPUs, como e2-standard-4. Consulte o guia de instalação do
Anthos Service Mesh para ver detalhes sobre os requisitos. Se você precisar alterar
o tipo de máquina do cluster, consulte
Como migrar cargas de trabalho para diferentes tipos de máquina.
Para aproveitar o provisionamento automatizado de domínios de teste,
o Cloud Service Mesh usa um gateway de entrada e um serviço chamado istio-ingress
no namespace istio-system. Para ativar a criação do gateway durante
a instalação do recurso, use --option legacy-default-ingressgateway
do script de instalação de asmcli.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2024-10-08 UTC."],[],[],null,["# Prerequisites for clusters on Google Cloud\n\nBefore you install Knative serving in your cluster on Google Cloud, you must\nfirst ensure that you meet the following requirements:\n\n- Review and understand the\n [access permissions of components in Knative serving](/kubernetes-engine/enterprise/knative-serving/docs/install/permissions).\n\n- You must ensure that you have adequate permissions in your Google Cloud project\n to meet the installation requirements for your cluster,\n fleet, and Cloud Service Mesh:\n\n - If you have the [*Owner*](/iam/docs/understanding-roles#basic) role for the Google Cloud project, then you have more than the necessary permissions to create clusters, install, and then configure Knative serving.\n - Note that the\n [Cloud Service Mesh permissions requirements](/service-mesh/v1.18/docs/installation-permissions)\n also meet all the permission requirements for installing and configuring\n Knative serving.\n\n - Using other roles and the minimum requirements:\n\n Depending on your organization, you can also meet the permission\n requirements through a combination of the following predefined roles:\n - Google Cloud project permissions: [Basic *Editor* role](/iam/docs/understanding-roles#basic)\n\n - Fleet permissions:\n [*GKE Hub Admin*](/iam/docs/understanding-roles#gke-hub-roles)\n or a role that includes the following permissions:\n\n - `gkehub.features.create`\n - `gkehub.features.update`\n - Cluster permissions:\n [A Kubernetes Engine Admin Role](/iam/docs/understanding-roles#kubernetes-engine-roles):\n\n - *Kubernetes Engine Admin*\n - *Kubernetes Engine Cluster Admin*\n- A cluster with the following configuration is required:\n\n - A supported\n [Google Kubernetes Engine cluster](/anthos/docs/setup/set-up-google-cloud). Note that\n GKE clusters that have Windows Server node pools are\n unsupported.\n\n - Registered to a fleet:\n\n [Go to GKE clusters](https://console.cloud.google.com/kubernetes/list/overview)\n | **Tip:** Workload Identity Federation for GKE allows you to authenticate to Google Cloud services and it's also required by Cloud Service Mesh. Enabling fleet Workload Identity Federation in your cluster during fleet registration can reduce the configuration and deployment time.\n\n To learn how to register your cluster and enable Workload Identity Federation for GKE in\n your fleet, see\n [Registering a cluster](/kubernetes-engine/fleet-management/docs/register/gke). Supported cluster types outside Google Cloud are registered by default.\n - In-cluster [Cloud Service Mesh version 1.18 or later is\n installed](/service-mesh/v1.18/docs/unified-install/install-anthos-service-mesh).\n Additionally, note the following prerequisites:\n\n - The [Google-managed Cloud Service Mesh control plane](/service-mesh/docs/supported-features-mcp) is currently not fully supported by Knative serving. Use the in-cluster control plane instead.\n - Cloud Service Mesh requires that your cluster use a machine type with at least 4 vCPUs, such as `e2-standard-4`. See the Cloud Service Mesh installation guide for details about requirements. If you need to change your existing cluster's machine type, see [Migrating workloads to different machine types](/kubernetes-engine/docs/tutorials/migrating-node-pool).\n - In order to benefit from the automated provisioning of test domains - Cloud Service Mesh uses an ingress gateway and a service named `istio-ingress` in namespace `istio-system`. To enable creation of the gateway during the feature installation use `--option legacy-default-ingressgateway` of `asmcli` installation script.\n- [The command-line environment must be set up](/kubernetes-engine/enterprise/knative-serving/docs/install/on-gcp/command-line-tools).\n\n- The following APIs must be enabled in your Google Cloud project:\n\n - Google Kubernetes Engine API: Build and manage container-based applications.\n - Cloud Build API: Create and manage builds.\n - Container Registry API: Push and pull images in Container Registry.\n\n [Enable the APIs in the Google Cloud console](https://console.cloud.google.com/start/api?id=container.googleapis.com,containerregistry.googleapis.com,cloudbuild.googleapis.com)"]]