This is the first of a series of posts explaining why administrators and architects should to use Google Kubernetes Engine (GKE) to create batch processing systems
Innovation is happening more quickly now that Kubernetes is a top container orchestration technology for managing and delivering containerized applications
The Kubernetes Job API allows you to manage Jobs A Job starts one or more Pods and keeps trying to run them until a predetermined number of them finish successfully
The Job records the successful completions of Pods as they happen The job or assignment is deemed finished after a predetermined number of successful completions
Nodes, or Compute Engine virtual machines (VMs), are joined together to form clusters in a GKE environment
The biggest Kubernetes clusters that a managed provider can presently host are supported by GKE. For many bulk use cases, a cluster size of 15,000 nodes
An option to managing several single-tenant clusters and access control is GKE cluster multi-tenancy According to this approach, several users and/or workloads referred to as “tenants” share a multi-tenant cluster
You have control over which logs and metrics, if any, are delivered from your GKE cluster to Cloud Logging and Cloud Monitoring thanks to GKE’s integration with Google Cloud’s operations suite