I am creating a GKE cluster (4 nodes) and deploying applications on it.
While doing that the API server become unresponsive for a few minutes.
Want to create a GKE cluster with scaled control plane.
I am creating a GKE cluster (4 nodes) and deploying applications on it.
While doing that the API server become unresponsive for a few minutes.
Want to create a GKE cluster with scaled control plane.
As I mentioned in the comment section, you cannot change anything in the GKE master, its fully managed by googler.
In overall GKE Documentation you can find information that it's managed by GKE SRE
Fully managed: GKE clusters are fully managed by Google Site Reliability Engineers (SREs), ensuring your cluster is available and up-to-date.
One of the reasons why only Google can manage your cluster is described Vulnerability and patch management part of GKE documentation, however there are a few more reasons.
GKE control plane components are managed by a team of Google site reliability engineers, and are kept up to date with the latest security patches. This includes patches to the host operating system, Kubernetes components, and containers running on the control plane VMs.
Additional information you can find also in Control plane security:
Under the Shared Responsibility Model, Google manages the GKE control plane components for you. The control plane includes the Kubernetes API server, etcd, and other controllers. Google is responsible for securing the control plane, though you might be able to configure certain options based on your requirements. You are responsible for securing your nodes, containers, and Pods.
Regarding the second part, where you want to have multiple masters, you can achieve it creating Regional Cluster.
In contrast to zonal clusters that have a single control plane in a single zone, regional clusters increase the availability of both a cluster's control plane and its nodes by replicating them across multiple zones in a region. This provides the advantages of multi-zonal clusters
...
The control plane is replicated across three zones of a region. For node pools, you can manually specify the zone(s) in which the cluster's node pools run or you can use the default configuration, which replicates each node pool across three zones of the control plane's region. All zones must be within the same region as the cluster's control plane.
To sum up:
Regional
cluster instead of Zonal