You can inspect the pods running in the kube-system namespace by running kubectl get pods --namespace=kube-system
Some of those pods can be disabled via the GKE API (e.g. turn off dashboard, disable logging and/or monitoring if you don't need them). On Fri, Nov 17, 2017 at 2:40 AM, 'Vitalii Tamazian' via Kubernetes user discussion and Q&A <kubernetes-users@googlegroups.com> wrote: > Hi! > I have small java/alpine linux microservice that previously was running > fine on n1-standard-1 (1 vCPU, 3.75 GB memory) on GCP. > But after nodepool upgrade to 1.6.11 my service become "unschedulable". > And I was able to fix it only by adding the second node. So my cluster now > runs on 2 vCPUs, 7.50 GB, which imo is a quite overkill for the service > which actually uses up to 300Mb of memory. The average cpu usage is very > low. > There is still a single pod in the cluster. > > Is there any way to check what consumes the rest of the resources? Is > there a way to make it schedulable on 1 node again? > > Thanks, > Vitalii > > -- > You received this message because you are subscribed to the Google Groups > "Kubernetes user discussion and Q&A" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to kubernetes-users+unsubscr...@googlegroups.com. > To post to this group, send email to kubernetes-users@googlegroups.com. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
