Hi anlex_N,
Welcome to Google Cloud Community!
In Kubernetes (GKE), Services refer to Kubernetes resources that provide stable networking endpoints and abstract access to a set of Pods. Common Service types include:
- ClusterIP
- NodePort
- LoadBalancer
- ExternalName
Workloads, on the other hand, represent the compute resources running containerized applications. These include:
- Pods
- Deployment
- Job
- CronJob
- StatefulSets
- DaemonSets
In the context of a Cloud Service Mesh, workloads are the instances (Pods, VMs, or Pod-to-Pod communications) that participate in the mesh, while services are logical groups of workloads that are addressable within the mesh.
According to the official documentation, one supported feature of Cloud Service Mesh is the ability for a cluster to scale up to 1,000 services meaning you can define up to 1,000 different services with associated routing policies, security settings, and telemetry configurations. Similarly, it supports up to 5,000 workloads Pods or VMs (your application instances).
Note: once Cloud Service Mesh is enabled for a particular membership (i.e GKE cluster), all kubernetes services in the cluster are translated to Cloud Service Mesh services, including those that target workloads without a Cloud Service Mesh sidecar. Cloud Service Mesh creates Zonal Network Endpoint Groups for all services in the GKE cluster. If the cluster is regional, network endpoint groups are created for all node pool zones in the region.
Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.
LinkedIn
Twitter
