Boost your Workload Automation console in a GKE cluster with Google Cloud SQL and session affinity enabled for the load balancer
In this blog, we are going to walk you through enabling session affinity for the Dynamic Workload Console (console) deployed in a Google Kubernetes Engine (GKE) cluster that uses an HTTP(S) load balancer network service that leverages an instance of Google Cloud SQL for SQL Server managed database. In a GKE cluster environment, a backend service defines how the HTTP(S) cloud load balancing network service distributes incoming traffic. By default, the method for distributing new connections uses a hash calculated based on five pieces of information: The client's IP address.The source port.The load balancer's internal forwarding rule IP address.The destination port.The protocol. You can modify the traffic distribution method for HTTP(S) traffic by specifying a session affinity option.