I’m using GKE with more than three spot instance node pools, each with different machine types. I want to globally prioritize one node pool over the others so that the autoscaler scales up nodes in the preferred pool first, falling back to other pools only if the preferred one is unavailable.

I am trying to configure healthcheck with GKE Ingress Controller + Application Loadbalancer, but having issues as my health/status ports is not exposed as a Kubernetes’s Service (due to the sensitive nature)

I am trying to configure healthcheck with GKE Ingress Controller + Application Loadbalancer, but having issues as my health/status ports is not exposed as a Kubernetes’s Service (due to the sensitive nature)

I am trying to configure healthcheck with GKE Ingress Controller + Application Loadbalancer, but having issues as my health/status ports is not exposed as a Kubernetes’s Service (due to the sensitive nature)

I am trying to configure healthcheck with GKE Ingress Controller + Application Loadbalancer, but having issues as my health/status ports is not exposed as a Kubernetes’s Service (due to the sensitive nature)

I have created a cluster in gke and then create few deployments specific to my application. My question is how do i delete an specific image that has been up there because even though i have set my imagePullPolicy: Always in my deployment file it does not pull the latest image, instead it uses the cached image.

I have a kubernetes cluster which needs to be replaced (not upgraded), and I’m trying to figure out how to do it as seamlessly as possible. In other situations I just destroy the old cluster and launch the new one, but in this case, there will be workloads running in the old cluster that need to be allowed to run to completion.

enter image description here

I’m working on setting up an environment where I can dynamically create Jupyter notebook kernels as separate pods within a Google Kubernetes Engine (GKE) cluster. Each pod needs to have customizable CPU, memory, and GPU configurations. The goal is to control these pods through a Python backend, handling actions like creating, deleting, and checking the status of pods.

I’m facing a puzzling situation with resource usage in my Kubernetes namespace.