Produk yang dijelaskan dalam dokumentasi ini, Cluster Anthos di AWS (generasi sebelumnya), kini berada dalam mode pemeliharaan. Semua penginstalan baru harus menggunakan produk generasi saat ini, cluster Anthos di AWS.
Untuk terhubung ke resource GKE di AWS, lakukan langkah-langkah
berikut. Pilih apakah Anda memiliki VPC AWS yang sudah ada (atau koneksi langsung ke VPC Anda) atau membuat VPC khusus saat membuat layanan pengelolaan.
VPC yang ada
Jika Anda memiliki koneksi langsung atau VPN ke VPC yang ada, hapus baris
env HTTP_PROXY=http://localhost:8118 dari perintah dalam topik ini.
VPC Khusus
Saat Anda membuat layanan pengelolaan di VPC khusus, GKE di AWS menyertakan host bastion di subnet publik.
Untuk terhubung ke layanan pengelolaan, lakukan langkah-langkah berikut:
Untuk membuka tunnel, jalankan skrip bastion-tunnel.sh. Tunnel meneruskan
ke localhost:8118.
Untuk membuka tunnel ke bastion host, jalankan perintah berikut:
./bastion-tunnel.sh-N
Pesan dari tunnel SSH akan muncul di jendela ini. Saat Anda siap untuk
menutup koneksi, hentikan proses dengan menggunakan Control+C atau
menutup jendela.
Buka terminal baru dan ubah ke direktori anthos-aws Anda.
cd anthos-aws
Pastikan Anda dapat terhubung ke cluster dengan kubectl.
Output-nya mencakup URL untuk server API layanan pengelolaan.
Perintah di bagian berikut mengasumsikan bahwa Anda menggunakan host bastion ini.
Jika Anda tidak menggunakan bastion host, hapus baris yang berisi HTTP_PROXY.
Menghubungkan ke layanan pengelolaan dengan kubectl
Untuk terhubung ke layanan pengelolaan dengan alat kubectl, lakukan langkah-langkah berikut:
Dari direktori anthos-aws, gunakan
anthos-gke untuk mengganti konteks ke layanan pengelolaan Anda.
cd anthos-aws
anthos-gke aws management get-credentials
Menghubungkan ke cluster pengguna dengan kubectl
Untuk terhubung ke cluster pengguna dengan alat kubectl, lakukan langkah-langkah berikut:
Dari direktori anthos-aws, gunakan
anthos-gke untuk beralih konteks ke cluster pengguna Anda.
cd anthos-aws
env HTTPS_PROXY=http://localhost:8118 \
anthos-gke aws clusters get-credentials CLUSTER_NAME
Ganti CLUSTER_NAME dengan nama cluster pengguna Anda.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-07-14 UTC."],[],[],null,["# Connecting to your cluster with kubectl\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\nThe bastion host\n----------------\n\nTo connect to your GKE on AWS resources, perform the following\nsteps. Select if you have an existing AWS VPC (or direct connection to\nyour VPC) or created a dedicated VPC when creating your management service. \n\n### Existing VPC\n\nIf you have a direct or VPN connection to an existing VPC, omit the line\n`env HTTP_PROXY=http://localhost:8118` from commands in this topic.\n\n### Dedicated VPC\n\nWhen you create a management service in a dedicated VPC,\nGKE on AWS includes a\n[bastion](https://en.wikipedia.org/wiki/Bastion_host) host in a\npublic subnet.\n| **Important:** If you restart your terminal session or the SSH connection is lost, you need to re-launch the `bastion-tunnel.sh` script.\n\nTo connect to your management service, perform the following steps:\n\n1. Change to the directory with your GKE on AWS configuration.\n You created this directory when\n [Installing the management service](/kubernetes-engine/multi-cloud/docs/aws/previous-generation/how-to/installing-management).\n\n ```sh\n cd anthos-aws\n ```\n\n \u003cbr /\u003e\n\n2. To open the tunnel, run the `bastion-tunnel.sh` script. The tunnel forwards\n to `localhost:8118`.\n\n To open a tunnel to the bastion host, run the following command: \n\n ./bastion-tunnel.sh -N\n\n Messages from the SSH tunnel appear in this window. When you are ready to\n close the connection, stop the process by using \u003ckbd\u003eControl+C\u003c/kbd\u003e or\n closing the window.\n3. Open a new terminal and change into your `anthos-aws` directory.\n\n ```sh\n cd anthos-aws\n ```\n4. Check that you're able to connect to the cluster with `kubectl`.\n\n env HTTPS_PROXY=http://localhost:8118 \\\n kubectl cluster-info\n\n The output includes the URL for the management service API server.\n\nThe commands in the following sections assume you are using this bastion host.\nIf you are not using the bastion host, remove the lines containing `HTTP_PROXY`.\n\nConnecting to your management service with kubectl\n--------------------------------------------------\n\nTo connect to your management service with the `kubectl` tool, perform the\nfollowing steps:\n\nFrom your `anthos-aws` directory, use\n`anthos-gke` to switch context to your management service.\n\n```sh\ncd anthos-aws\nanthos-gke aws management get-credentials\n```\n| **Note:** `anthos-gke` uses the credentials you specified when you ran `aws configure`.\n\n\u003cbr /\u003e\n\nConnecting to your user clusters with kubectl\n---------------------------------------------\n\nTo connect to your user clusters with the `kubectl` tool, perform the\nfollowing steps:\n\nFrom your `anthos-aws` directory, use\n`anthos-gke` to switch context to your user cluster.\n\n```sh\ncd anthos-aws\nenv HTTPS_PROXY=http://localhost:8118 \\\n anthos-gke aws clusters get-credentials CLUSTER_NAME\n```\nReplace \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e with your user cluster name.\n\n\u003cbr /\u003e"]]
