How to run elasticsearch pod in gke autopilot mode about kubernetes-engine-samples HOT 6 CLOSED

On Wed, Mar 17, 2021 at 11:29 PM askmeegs ***@***.***> wrote: Hello, sorry you're encountering this friction. What are the CPU and memory specs of your cluster? How many nodes? The elasticsearch pod events suggest your cluster doesn't have enough CPU and memory Normal TriggeredScaleUp 3m43s cluster-autoscaler pod triggered scale-up: [{https://content.googleapis.com/compute/v1/projects/lexical-pattern-305514/zones/us-east1-c/instanceGroups/gk3-autopilot-cluster-1-nap-1535p6rr-5687b4d4-grp 0->1 (max: 1000)}] Warning FailedScheduling 3m34s (x3 over 4m39s) gke.io/optimize-utilization-scheduler 0/2 nodes are available: 2 Insufficient cpu, 2 Insufficient memory. Warning FailedScheduling 3m2s (x2 over 3m2s) gke.io/optimize-utilization-scheduler 0/3 nodes are available: 1 Insufficient ephemeral-storage, 2 Insufficient cpu, 2 Insufficient memory. Warning FailedScheduling 2m42s (x3 over 2m54s) gke.io/optimize-utilization-scheduler 0/3 nodes are available: 1 node(s) had taint {node.kubernetes.io/not-ready: }, that the pod didn't tolerate, 2 Insufficient cpu, 2 Insufficient memory. It seems like this happened despite a cluster scale-up. I recommend looking at the Autopilot documentation <https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview>, and the various constraints of an autopilot cluster - for instance the resource section <https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview#range_ratio>. Also, I notice that your pods are privileged, and this isn't allowed in autopilot <https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview#no_privileged_pods> . — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#172 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKNX3RMHTFG6OQ6FTZXEEY3TEDUZRANCNFSM4YT35XLA> .

On Thu, Mar 25, 2021 at 4:36 AM Viacheslav Vasilyev < ***@***.***> wrote: access to GKE-Autopilot managed nodes is not allowed, hence you cannot change node-level settings like vm.max_map_count — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#172 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKNX3RJ6FX3QHCSVXBTYYX3TFJWBFANCNFSM4YT35XLA> .