Halaman ini menyediakan serangkaian rekomendasi untuk perencanaan, perancangan, deployment,
penskalaan, dan pengoperasian workload berukuran besar di cluster Google Kubernetes Engine (GKE). Sebaiknya ikuti rekomendasi ini
agar workload penskalaan Anda tetap berada dalam
tujuan tingkat layanan (SLO).
Rekomendasi yang tersedia untuk skalabilitas
Sebelum merencanakan dan merancang arsitektur GKE, petakan parameter khusus untuk
workload Anda (misalnya jumlah pengguna aktif, perkiraan waktu respons,
resource komputasi yang diperlukan) dengan resource yang digunakan oleh Kubernetes (seperti Pod,
Layanan, dan 'CustomResourceDefinition'). Setelah informasi ini dipetakan, tinjau
rekomendasi skalabilitas GKE.
Rekomendasi skalabilitas dibagi berdasarkan cakupan perencanaan berikut:
Merencanakan skalabilitas: Untuk mempelajari praktik terbaik umum dalam
merancang workload dan cluster guna mendapatkan performa terbaik saat dijalankan
pada cluster kecil dan besar. Rekomendasi ini berguna bagi para arsitek,
administrator platform, dan developer Kubernetes. Untuk mempelajari lebih lanjut, lihat
Merencanakan skalabilitas.
Merencanakan cluster GKE berukuran besar: Untuk mempelajari cara merencanakan cluster GKE
berukuran sangat besar. Pelajari batas Kubernetes dan GKE yang diketahui,
serta cara agar batas tersebut tidak tercapai. Rekomendasi ini berguna bagi para arsitek
dan administrator platform. Untuk mempelajari lebih lanjut, lihat
Merencanakan cluster GKE besar.
Merencanakan workload besar: Untuk mempelajari cara merencanakan arsitektur yang menjalankan workload Kubernetes besar di GKE. Panduan ini mencakup rekomendasi cara mendistribusikan
workload di antara project dan cluster, serta menyesuaikan kuota yang diperlukan
workload ini. Rekomendasi ini berguna bagi para arsitek dan administrator platform.
Untuk mempelajari lebih lanjut, lihat
Merencanakan workload besar.
Rekomendasi skalabilitas ini bersifat umum untuk GKE dan berlaku pada
mode GKE Standard dan GKE Autopilot. GKE Autopilot menyediakan dan mengelola
infrastruktur dasar cluster bagi Anda, sehingga beberapa rekomendasi
tidak berlaku.
[[["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-08-04 UTC."],[],[],null,["# About GKE Scalability\n\n[Autopilot](/kubernetes-engine/docs/concepts/autopilot-overview) [Standard](/kubernetes-engine/docs/concepts/choose-cluster-mode)\n\n*** ** * ** ***\n\nThis page provides a set of recommendations for planning, architecting, deploying, scaling, and operating large workloads on Google Kubernetes Engine (GKE) clusters. We recommend you follow these recommendations to keep your scaling workloads within [service-level objectives (SLOs)](https://landing.google.com/sre/sre-book/chapters/service-level-objectives).\n\n\u003cbr /\u003e\n\nAvailable recommendations for scalability\n-----------------------------------------\n\nBefore planning and designing a GKE architecture, map parameters specific to your\nworkload (for example the number of active users, expected response time,\nrequired compute resources) with the resources used by Kubernetes (such as Pods,\nServices, and 'CustomResourceDefinition'). With this information mapped, review\nthe GKE scalability recommendations.\n\nThe scalability recommendations are divided based in the following planning scopes:\n\n- **Plan for scalability** : To learn about the general best practices for designing your workloads and clusters for reliable performance when running on both small and large clusters. These recommendations are useful for architects, platform administrators, and Kubernetes developers. To learn more, see [Plan for scalability](/kubernetes-engine/docs/concepts/planning-scalability).\n- **Plan for large-size GKE clusters** : To learn how to plan to run very big-size GKE clusters. Learn about known limits of Kubernetes and GKE and ways to avoid reaching them. These recommendations are useful for architects and platform administrators. To learn more, see [Plan for large GKE clusters](/kubernetes-engine/docs/concepts/planning-large-clusters).\n- **Plan for large workloads** : To learn how to plan architectures that run large Kubernetes workloads on GKE. It covers recommendations for distributing the workload among projects and clusters, and adjusting these workload required quotas. These recommendations are useful for architects and platform administrators. To learn more, see [Plan for large workloads](/kubernetes-engine/docs/concepts/planning-large-workloads).\n\nThese scalability recommendations are general to GKE and are applicable to both\nGKE Standard and GKE Autopilot modes. GKE Autopilot provisions and manages\nthe cluster's underlying infrastructure for you, therefore some recommendations\nare not applicable.\n| **Caution:** Test your planned cluster configuration before its implementation. Some design decisions might include fixed parameters, for example, CIDRs definition. Changing these parameters on existing clusters is not available and it requires cluster recreation.\n\nWhat's next?\n------------\n\n- [Plan for scalability](/kubernetes-engine/docs/concepts/planning-scalability).\n- [Plan for large GKE clusters](/kubernetes-engine/docs/concepts/planning-large-clusters)\n- [Plan for large workloads](/kubernetes-engine/docs/concepts/planning-large-workloads)\n- See our episodes about [building large GKE clusters](https://www.youtube.com/watch?v=542XwAPKh4g)."]]
