Memilih alat untuk mengelola siklus proses cluster
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Google Distributed Cloud memberi Anda pilihan alat untuk membuat cluster dan mengelola operasi siklus proses cluster (update, upgrade, dan hapus):
Alat command line bmctl, yang Anda jalankan di workstation admin
di pusat data lokal. Anda membuat
file konfigurasi
yang menjelaskan jaringan cluster, load balancing, dan fitur
cluster lainnya. Anda menentukan file ini di command line ke bmctl. Anda juga dapat menjalankan kubectl di workstation admin untuk mengupgrade dan mengupdate cluster serta menghapus cluster pengguna.
Google Cloud konsol, Google Cloud CLI, atau
Terraform,
yang dapat Anda jalankan dari komputer apa pun yang memiliki konektivitas jaringan ke
GKE On-Prem API.
Alat standar ini menggunakan GKE On-Prem API, yang berjalan di infrastruktur Google Cloud. Secara kolektif, alat standar disebut sebagai
klien GKE On-Prem API. Untuk mengelola siklus proses cluster, GKE On-Prem API harus menyimpan metadata tentang status cluster Anda diGoogle Cloud, di region Google Cloud yang Anda tentukan saat membuat cluster. Metadata ini memungkinkan API mengelola siklus proses
cluster dan tidak menyertakan data khusus beban kerja.
Apa pun alat yang Anda gunakan untuk membuat cluster, informasi yang
Anda kumpulkan dan berikan ke alat tersebut, seperti alamat IP
mesin node cluster dan VIP load balancer, akan sama.
Dengan pilihan ini, Anda dapat memilih alat terbaik untuk kasus penggunaan dan
lingkungan Anda. Contoh:
Untuk penginstalan pertama di lingkungan pengembangan, Anda mungkin
ingin menggunakan konsol karena antarmuka pengguna memberikan
panduan dan bantuan tambahan.
Jika organisasi Anda sudah menggunakan gcloud CLI atau Terraform untuk mengelola resource Google Cloud lainnya, Anda mungkin juga ingin menggunakan alat ini untuk Google Distributed Cloud.
Jika organisasi Anda memiliki persyaratan atau batasan peraturan, Anda
mungkin perlu membatasi ketergantungan pada Google Cloud dan menggunakan bmctl di
workstation admin untuk membuat cluster dan mengelola siklus proses cluster.
Jika membuat cluster dengan bmctl, Anda dapat
mendaftarkan cluster dengan GKE On-Prem API
setelah cluster dibuat, yang memungkinkan Anda juga menggunakan klien GKE On-Prem API.
Keterbatasan pada klien GKE On-Prem API
Alat bmctl dikirimkan dengan rilis pertama Google Distributed Cloud, dan merupakan alat yang paling matang dalam hal fitur yang didukungnya. Sebaiknya
tinjau fungsi untuk klien GKE On-Prem API saat membuat
pilihan. Daftar berikut merangkum batasan saat ini. Periksa daftar ini dari waktu ke waktu seiring perkembangan klien GKE On-Prem API.
Cluster admin dan pengguna adalah satu-satunya jenis cluster yang didukung
Versi minor atau patch terbaru tidak tersedia di GKE On-Prem API hingga 7 hingga 10 hari setelah rilis
[[["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-09-01 UTC."],[],[],null,["Google Distributed Cloud provides you a choice of tools to create clusters and\nmanage the cluster lifecycle operations (update, upgrade, and delete):\n\n- The command-line tool `bmctl`, which you run on your admin workstation in your on-premises data center. You create a [configuration file](/kubernetes-engine/distributed-cloud/bare-metal/docs/reference/cluster-config-ref) that describes the cluster network, load balancing, and other cluster features. You specify this file on the command line to `bmctl`. You can also run `kubectl` on your admin workstation to upgrade and update clusters and to delete user clusters.\n- The Google Cloud console, Google Cloud CLI, or [Terraform](https://www.terraform.io), which you can run from any computer that has network connectivity to the [GKE On-Prem API](/anthos/clusters/docs/on-prem-api/reference/rest). These standard tools use the GKE On-Prem API, which runs on Google Cloud infrastructure. Collectively, the standard tools are referred to as the *GKE On-Prem API clients*. To manage the lifecycle of your clusters, the GKE On-Prem API must store metadata about your cluster's state in Google Cloud, in the Google Cloud region that you specify when creating the cluster. This metadata lets the API manage the cluster lifecycle and doesn't include workload-specific data.\n\nNo matter which tool you use to create clusters, the information that\nyou gather and provide to the tool, such as the IP addresses\nof cluster node machines and load balancer VIPs, is the same.\n\nThis selection lets you choose the best tool for your use case and\nenvironment. For example:\n\n- For your first installations in a development environment, you might want to use the console because the user interface provides additional guidance and help.\n- If your organization already uses the gcloud CLI or Terraform to manage other Google Cloud resources, you will probably want to use these tools for Google Distributed Cloud as well.\n- If your organization has regulatory requirements or restrictions, you might need to limit your reliance on Google Cloud and use `bmctl` on your admin workstation to create clusters and manage cluster lifecycle.\n\nIf you create a cluster with `bmctl`, you can\n[enroll the cluster with the GKE On-Prem API](/kubernetes-engine/distributed-cloud/bare-metal/docs/how-to/enroll-cluster)\nafter the cluster is created, which lets you also use the GKE On-Prem API\nclients.\n\nLimitations with the GKE On-Prem API clients\n\nThe `bmctl` tool was shipped with the first release of Google Distributed Cloud,\nand it is the most mature as far as features that it supports. We recommend that\nyou review the functionality for the GKE On-Prem API clients when making a\nchoice. The following list summarizes current limitations. Check this list from\ntime to time as the GKE On-Prem API clients evolve.\n\n- Admin and user clusters are the only supported cluster types\n\n- The latest minor or patch versions aren't available in the GKE On-Prem API\n until 7 to 10 days after the release\n\n- The following advanced networking features aren't supported:\n\n - [IPv4/IPv6 dual-stack networking](/kubernetes-engine/distributed-cloud/bare-metal/docs/how-to/dual-stack-networking)\n - [IPv4 flat mode network model](/kubernetes-engine/distributed-cloud/bare-metal/docs/how-to/flat-network)\n\nWhat's next\n\n- `bmctl`\n\n - [Cluster configuration field reference](/kubernetes-engine/distributed-cloud/bare-metal/docs/reference/cluster-config-ref#cluster_configuration_fields)\n- gcloud CLI\n\n - [`gcloud container bare-metal clusters`](/sdk/gcloud/reference/container/bare-metal/clusters)\n\n - [`gcloud container bare-metal node-pools`](/sdk/gcloud/reference/container/bare-metal/node-pools)\n\n - [`gcloud container bare-metal admin-clusters`](/sdk/gcloud/reference/container/bare-metal/admin-clusters)\n\n- Terraform\n\n - [`google_gkeonprem_bare_metal_cluster`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/gkeonprem_bare_metal_cluster)\n\n - [`google_gkeonprem_bare_metal_node_pool`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/gkeonprem_bare_metal_node_pool)\n\n - [`google_gkeonprem_bare_metal_admin_cluster`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/gkeonprem_bare_metal_admin_cluster)"]]
