Create a cluster in GKE Autopilot mode
In Autopilot mode, Google manages most of the infrastructure and provides a more managed K8s experience than GKE Standard modCreate an Autopilot cluster by specifying a name and region. After the cluster is created, you can deploy your workload through Kubernetes and Google will take care of the rest, including:
Nodes: Automated node provisioning, scaling, and maintenance Networking: VPC-native traffic routing for public or private clusters Security: Shielded GKE Nodes and Workload Identity Telemetry: Cloud Operations logging and monitoring
- When creating a cluster, Google cloud asks for Network configurations for the cluster
Public clusters: Choose a public cluster to configure access from public networks to the cluster's workloads. Routes aren't created automatically. You cannot change this setting after the cluster is created.
Private clusters: Choose a private cluster to assign internal IP addresses to Pods and nodes. This isolates the cluster's workloads from public networks. You cannot change this setting after the cluster is created. In this case, after you create the cluster, configure Cloud NAT to enable outbound internet connections from your cluster, Learn more Deployments
- a replicated, stateless application on your cluster Pods
- the smallest deployable unit in Kubernetes Services
- allow your application to receive traffic Autoscaling pods
- scale the application based on load or custom metrics
Pods that are running inside Kubernetes are running on a private, isolated network. By default they are visible from other pods and services within the same Kubernetes cluster, but not outside that network Every Pod has a unique IP address And it is reachable from all other Pods in the K8s cluster A pod is a host, just like your laptop, having an ip-address and a range of ports that can be alloted to containers A container runs on a specific port inside a pod In a Kubernetes environment, when services are deployed within the same namespace , they can communicate with each other using the service name as the hostname e.g. in the following snippet from appsetting.json form a .net core project, ' document-api' is the name of the service "DocumentApiConfiguration" : { "BaseUrl" : "http://document-api/" } What if I want to access a service from another namespace? When you want to access a service from another namespace in Kubernetes, you typica...
Comments
Post a Comment