Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini merekomendasikan strategi workload container Kubernetes yang membuat aplikasi Anda lebih toleran terhadap kesalahan di multi-zona Google Distributed Cloud (GDC) dengan air gap. GDC mendukung aplikasi container native Kubernetes yang banyak digunakan dan didukung di Google Kubernetes Engine (GKE).
Halaman ini ditujukan bagi developer dalam grup operator aplikasi, yang bertanggung jawab membuat workload aplikasi untuk organisasi mereka. Untuk mengetahui informasi selengkapnya, lihat dokumentasi Audiens untuk GDC yang terisolasi dari internet.
Pertimbangan Kubernetes untuk aplikasi HA
Mencapai ketersediaan tinggi (HA) di Kubernetes tidak hanya terbatas pada bidang
kontrol. Anda juga harus mendesain dan men-deploy workload container di lingkungan air-gap Google Distributed Cloud (GDC) dengan tangguh. Kubernetes menawarkan beberapa mekanisme canggih untuk meminimalkan periode nonaktif dan menyediakan layanan dengan ketersediaan tinggi, bahkan saat menghadapi masalah infrastruktur atau selama pemeliharaan rutin. Topik berikut adalah strategi utama yang perlu dipertimbangkan untuk HA:
Mempertahankan ketersediaan dengan replika dan penskalaan otomatis: Anda harus memiliki instance aplikasi yang berjalan dalam jumlah yang cukup untuk menyediakan HA.
ReplicaSet: Resource ReplicaSet mempertahankan sekumpulan replika pod identik yang stabil dan berjalan pada waktu tertentu. Jika pod gagal atau dihentikan, pengontrol ReplicaSet akan otomatis membuat pod baru untuk menggantikannya. Lihat dokumentasi Kubernetes ReplicaSet untuk mengetahui informasi selengkapnya.
Horizontal Pod Autoscaler (HPA): Meskipun ReplicaSet mempertahankan jumlah replika yang tetap, HPA secara otomatis menyesuaikan jumlah ini berdasarkan metrik yang diamati seperti pemakaian CPU atau penggunaan memori. Hal ini memungkinkan aplikasi Anda menangani lonjakan beban. Lihat dokumentasi Kubernetes tentang Penskalaan Otomatis Pod Horizontal untuk mengetahui informasi selengkapnya.
[[["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-04 UTC."],[],[],null,["# Kubernetes workloads for high availability\n\nThis page recommends Kubernetes container workload strategies that make your\napplication more fault tolerant in a Google Distributed Cloud (GDC) air-gapped multi-zone\nuniverse. GDC supports Kubernetes-native container\napplications that are widely consumed and supported on\nGoogle Kubernetes Engine (GKE).\n\nThis page is for developers within the application operator group, who are\nresponsible for creating application workloads for their organization. For more\ninformation, see\n[Audiences for GDC air-gapped documentation](/distributed-cloud/hosted/docs/latest/gdch/resources/audiences).\n\nKubernetes considerations for HA apps\n-------------------------------------\n\nAchieving high availability (HA) in Kubernetes goes beyond just the control\nplane. You must also design and deploy container workloads in your\nGoogle Distributed Cloud (GDC) air-gapped universe resiliently. Kubernetes offers several\npowerful mechanisms to minimize downtime and provide highly available services\neven when facing infrastructure issues or during routine maintenance. The\nfollowing topics are key strategies to consider for HA:\n| **Important:** To access the URLs listed on this page, you must connect to the internet. The URLs are provided to access outside of your air-gapped environment.\n\n- **Maintain availability with replicas and autoscale**: You must have enough\n running instances of your application to provide HA.\n\n - `ReplicaSet`: A `ReplicaSet` resource maintains a stable set of\n identical pod replicas are running at any given time. If a pod fails or is\n terminated, the `ReplicaSet` controller automatically creates a new pod to\n replace it. See\n [ReplicaSet](https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/)\n Kubernetes documentation for more information.\n\n - Horizontal Pod Autoscaler (HPA): While a `ReplicaSet` maintains a fixed\n number of replicas, the HPA automatically adjusts this number based on\n observed metrics like CPU utilization or memory usage. This allows your\n application to handle load spikes. See\n [Horizontal Pod Autoscaling](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/)\n Kubernetes documentation for more information.\n\n- **Minimize downtime with `PodDisruptionBudget` (PDB)** : See\n [Specifying a Disruption Budget for your Application](https://kubernetes.io/docs/tasks/run-application/configure-pdb/)\n Kubernetes documentation for more information.\n\n- **Spread your risk with anti-affinity rules** : See\n [Affinity and anti-affinity](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity)\n Kubernetes documentation for more information.\n\n- **Health checks with liveness, readiness, and startup probes** : See\n [Configure Liveness, Readiness and Startup Probes](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/)\n Kubernetes documentation for more information.\n\n- **Stable endpoints and load balancing with services** : See\n [Services](https://kubernetes.io/docs/concepts/services-networking/service/)\n Kubernetes documentation for more information.\n\n- **Graceful updates and rollbacks with deployments** : See\n [Rolling Back a Deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#rolling-back-a-deployment)\n Kubernetes documentation for more information.\n\n- **Set requests and limits for resources** : See\n [Resource Management for Pods and Containers](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/)\n Kubernetes documentation for more information.\n\nWhat's next\n-----------\n\n- [Start learning about Kubernetes](/kubernetes-engine/docs/learn/get-started-with-kubernetes)\n- [Container workloads in GDC](/distributed-cloud/hosted/docs/latest/gdch/application/ao-user/containers/containers-intro)\n- [Create a cluster to run container workloads](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/create-user-cluster)"]]
