O produto descrito nesta documentação, os clusters do Anthos na AWS (geração anterior), agora está no modo de manutenção. Todas as novas instalações precisam usar o produto de geração atual Clusters do Anthos na AWS.
Como se conectar ao cluster com o Console do Google Cloud
Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Com o Connect, é possível usar o Console do Google Cloud para gerenciar os clusters de usuário. Cada cluster de usuário criado automaticamente executa o agente do Connect e é registrado nele. Para mais informações, consulte
Visão geral do Connect.
Antes de começar
Antes de começar a usar o GKE na AWS, verifique se você executou as seguintes tarefas:
Selecione o cluster. A tela Detalhes do cluster do Kubernetes é exibida.
Clique no botão Fazer login.
Selecione Token e cole o token do Kubernetes que você copiou anteriormente.
Clique em "Fazer login".
Registrar o cluster
Para evitar que vários clusters se registrem no Connect com o mesmo nome, registre o cluster por meio da CLI do Google Cloud. Ao registrar um cluster, é preciso
executar a Google Cloud CLI na mesma rede que o cluster.
Para registrar o cluster, execute o seguinte comando:
MEMBERSHIP_NAME: o nome da assinatura que você escolher e que é
usado para representar exclusivamente o cluster que está sendo registrado na frota.
SERVICE_ACCOUNT_KEY_PATH: o caminho do arquivo local para o
arquivo JSON da chave privada da conta de serviço baixado como parte dos Pré-requisitos.
Esta chave de conta de serviço é armazenada como um secret chamado creds-gcp no namespace
gke-connect.
KUBECONFIG_CONTEXT: o contexto do cluster que está sendo registrado da forma
como aparece no arquivo kubeconfig. É possível conseguir esse valor a partir da linha de comando executando kubectl config current-context.
KUBECONFIG_PATH: o caminho de arquivo local em que
o kubeconfig que contém uma entrada para o cluster que está sendo registrado é armazenado.
O padrão é $KUBECONFIG se essa variável de ambiente estiver definida.
Caso contrário, o padrão será $HOME/.kube/config.
[[["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-06-26 UTC."],[],[],null,["# Connecting to your cluster with Google Cloud console\n\nWith Connect, you can use the Google Cloud console to manage your\nuser clusters. Each user cluster that you create automatically runs the\nConnect Agent and is registered with Connect. For more\ninformation, see\n[Connect overview](/anthos/multicluster-management/connect/overview).\n\nBefore you begin\n----------------\n\n\nBefore you start using GKE on AWS, make sure you have performed the following tasks:\n\n- Complete the [Prerequisites](/kubernetes-engine/multi-cloud/docs/aws/previous-generation/how-to/prerequisites).\n\n\u003c!-- --\u003e\n\n- Install a [management service](/kubernetes-engine/multi-cloud/docs/aws/previous-generation/how-to/installing-management).\n- Create a [user cluster](/kubernetes-engine/multi-cloud/docs/aws/previous-generation/how-to/creating-user-cluster).\n\nLogging into your cluster with Connect\n--------------------------------------\n\nYou can use the Google Cloud console to view, monitor, debug, and manage workloads\non your user clusters.\n\nTo log into your user clusters:\n\n1. From your `anthos-aws` directory, use\n `anthos-gke` to switch context to your user cluster.\n\n ```sh\n cd anthos-aws\n env HTTPS_PROXY=http://localhost:8118 \\\n anthos-gke aws clusters get-credentials CLUSTER_NAME\n ```\n Replace \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e with your user cluster name.\n\n \u003cbr /\u003e\n\n2. From a command line, use `kubectl` to set up a\n [Kubernetes service account](https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/)\n and a token in the `kube-system` namespace.\n\n This topic assumes the name of the service account is `admin-user`. \n\n env HTTPS_PROXY=http://localhost:8118 \\\n kubectl create serviceaccount -n kube-system admin-user\n\n3. Create a service account token Secret with `kubectl`.\n\n env HTTPS_PROXY=http://localhost:8118 \\\n kubectl apply -n kube-system -f - \u003c\u003c EOF\n apiVersion: v1\n kind: Secret\n metadata:\n name: admin-user-token\n annotations:\n kubernetes.io/service-account.name: admin-user\n type: kubernetes.io/service-account-token\n EOF\n\n4. Create a ClusterRoleBinding between the `cluster-admin` role and\n the Kubernetes service account.\n\n env HTTPS_PROXY=http://localhost:8118 \\\n kubectl create clusterrolebinding admin-user-binding \\\n --clusterrole cluster-admin --serviceaccount kube-system:admin-user\n\n5. Get the service account's Secret with `kubectl`.\n\n env HTTPS_PROXY=http://localhost:8118 \\\n kubectl get secret -n kube-system admin-user-token -o jsonpath='{$.data.token}' \\\n | base64 -d | sed $'s/$/\\\\\\n/g'\n\n6. Copy the secret to your clipboard.\n\n7. In the Google Cloud console, go to the **Google Kubernetes Engine clusters\n overview** page.\n\n [Go to GKE clusters](https://console.cloud.google.com/kubernetes/list/overview)\n8. Select the cluster. The **Kubernetes cluster details** screen appears.\n\n9. Click the **Login** button.\n\n10. Select **Token** and paste the Kubernetes token you copied earlier.\n Click Login.\n\n### Register your cluster\n\n| **Note:** The following section only applies to cluster versions 1.21 and lower.\n\nTo prevent multiple clusters from registering to Connect with the same\nname, you register the cluster through Google Cloud CLI. When you register a\ncluster, you must run the Google Cloud CLI from the same network as your cluster.\nTo register your cluster, run the following command: \n\n```\n gcloud container fleet memberships register MEMBERSHIP_NAME \\\n --context=KUBECONFIG_CONTEXT \\\n --kubeconfig=KUBECONFIG_PATH \\\n --service-account-key-file=SERVICE_ACCOUNT_KEY_PATH\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eMEMBERSHIP_NAME\u003c/var\u003e: the membership name that you choose and that is used to uniquely represent the cluster being registered to the fleet.\n- \u003cvar translate=\"no\"\u003eSERVICE_ACCOUNT_KEY_PATH\u003c/var\u003e: the local filepath to the service account's private key JSON file downloaded as part of Prerequisites. This service account key is stored as a secret named `creds-gcp` in the `gke-connect` namespace.\n- \u003cvar translate=\"no\"\u003eKUBECONFIG_CONTEXT\u003c/var\u003e: the cluster context of the cluster being registered as it appears in the kubeconfig file. You can get this value from the command line by running `kubectl config current-context`.\n- \u003cvar translate=\"no\"\u003eKUBECONFIG_PATH\u003c/var\u003e: the local filepath where your kubeconfig containing an entry for the cluster being registered is stored. This defaults to `$KUBECONFIG` if that environment variable is set; otherwise, this defaults to `$HOME/.kube/config`.\n\nWhat's next\n-----------\n\nRead the full documentation on\n[Logging into clusters](/anthos/multicluster-management/console/logging-in)\nwith Connect.\n\nLearn about multi-cluster management with\n[Connect](/anthos/multicluster-management/connect/overview)."]]
