Kubernetes Oracle (OCI) Tidak Bisa Autoscale Cluster/Node

Di dalam kubernetes ada beberapa jenis autoscale

Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings
Ink Drawings

Horizontal pod autoscale, menambah instance pod (Scale out). Sedangkan Vertical pod autoscale memperbesar spesifiaksi pod (cpu/memory) (Scale up). Kedua pod scaling ini juga bisa digabung. Untuk menentukan apakah mau scale up atau scale down, metrik defaultnya adalah utilisasi CPU, namun bisa juga memakai metrik lain (namun tidak resmi disupport).

Ketika pod di scale, pod akan di recreate, mencari node yang ada sisa tempat untuk diletakan pod nya. Namun bagaimana jika semua node penuh? solusinya adalah menggunakan cluster/node autoscale (Dengan menambah node baru).

Beberapa managed kubernetes dari cloud provider yang saya tahu mensupport cluster autoscale (mungkin ada beberapa yang tidak ada di ilst ini)

  • ali
    • https://www.alibabacloud.com/help/doc-detail/119099.htm
  • gcp
    • https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-autoscaler
  • aws
    • https://docs.aws.amazon.com/eks/latest/userguide/cluster-autoscaler.html
  • azure
    • https://docs.microsoft.com/en-us/azure/aks/cluster-autoscaler

Saat ini saya sedang menggunakan managed kubernetes dari oracle cloud (oracle container engine). Dan saya belum menemukan dokumentasi mengenai cluster autoscaling. Dokumentasi di https://docs.cloud.oracle.com/en-us/iaas/Content/ContEng/Tasks/contengautoscalingclusters.htm hanya menjelaskan autoscaling pod menggunakan hpa dan vpa.

Mungkin bisa di akalin dengan membuat service monitor sendiri, dan menggunakan api untuk menambah node di node pool (https://docs.cloud.oracle.com/en-us/iaas/Content/Identity/Reference/contengpolicyreference.htm#Details_for_Container_Engine_for_Kubernetes)

Leave a Reply

Please Connect to comment
  Subscribe  
Notify of