node-pool | project abandoned , please instead check hypepool | Blockchain library

I am trying to set up a Mongo DBon a specific node on GKE. I upgraded my current cluster using

How to change the existing GKE cluster to GKE private cluster? Will I be able to connect to the Kubectl API from internet based on firewall rules or should I have a bastion host? I don't want to implement Cloud Nat or nat gateway. I have a squid proxy VM that can handle internet access for pods. I just need to be able to connect to Kubectl to apply or modify anything.

I'm unsure how to modify the existing module I wrote to make the nodes private and I'm not sure if the cluster will get deleted if I try and apply the new changes related to private gke cluster.

How can I get the current size of a GKE node pool using the REST (or Node) API?

I'm managing my own worker pool using my Express app running on my cluster, and can set the size of the pool and track the success of the setSize operation, but I see no API for getting the current node count. The NodePool resource only includes the original node count, not the current count. I don't want to use gcloud or kubectl on one of my production VMs.

I could go around GKE and try to infer the size using the Compute Engine (GCE) API, but I haven't looked into that approach yet. Note that it seems difficult to get the node count even from Stack Driver. Has anyone found any workarounds to get the current node size?

I am having a problem where I am trying to restrict a deployment to work on avoid a specific node pool and nodeAffinity and nodeAntiAffinity don't seem to be working.

• We are running DOKS (Digital Ocean Managed Kubernetes) v1.19.3
• We have two node pools: infra and clients, with nodes on both labelled as such
• In this case, we would like to avoid deploying to the nodes labelled "infra"

For whatever reason, it seems like no matter what configuration I use, Kubernetes seems to schedule randomly across both node pools.

See configuration below, and the results of scheduling

deployment.yaml snippet

I have a regional cluster for redundancy. In this cluster I want to create a node-pool in just 1 zone in this region. Is this configuration possible? reason I trying this is, I want to run service like RabbitMQ in just 1 zone to avoid split, and my application services running on all zones in the region for redundancy.

I am using terraform to create the cluster and node pools, below is my config for creating region cluster and zone node pool

I have both Node Auto Provisioning and Autoscaling enabled on a GKE Cluster. Few queries on Auto Scaling.

For AutoScaling, the minimum nodes are 1 and the maximum number of nodes is 2. Few queries based on this setup.

I set the number of nodes to 0 using gcloud command

Does GKE supports vertical node auto-scaling?

For example:

I have a GKE cluster with only one node-pool and two nodes that node-pool, in case there is a requirement for more memory or CPU by any pod, I do not want any other nodes / compute instances to be created, is there a way in which the configuration of existing nodes change and extra memory / CPU get added?

Basically, existing instances / nodes get upgraded to become instances with higher configuration.

I am running a cluster on Google Kubernetes Engine and I am currently trying to switch from using an Ingress with external load balancing (and NodePort services) to an ingress with container-native load balancing (and ClusterIP services) following this documentation: Container native load balancing

To communicate with my services I am using the following ingress configuration that used to work just fine when using NodePort services instead of ClusterIP:

I had to move my .Net Core app from a Google App Engine to Google Kubernetes Engine because I need static IPs and sadly Google App Engine doesn't have that option.

I've managed to make a cluster and some pod, but in the logs I see: