https://stackoverflow.com/questions/48993286/is-it-possible-to-route-traffic-to-a-specific-pod?rq=1
You can guarantee session affinity with services, but not as you are describing. So, your customers 1-1000 won't use pod-1, but they will use all the pods (as a service makes a simple load balancing), but each customer, when gets back to hit your service, will be redirected to the same pod.
Note: always within time specified in (default 10800):
| kubectl get pods --all-namespaces | grep Evicted | awk '{print $2 " --namespace=" $1}' | xargs kubectl delete pod |
| # Show proxy settings | |
| function proxy_show(){ | |
| env | grep -e _PROXY -e _proxy | sort | |
| } | |
| # Configure proxy | |
| function proxy_on(){ | |
| # You may need to hardcode your password, proxy server, and proxy port | |
| # if the following variables do not exist | |
| export HTTP_PROXY="http://$USERNAME:$PASSWORD@$PROXY_SERVER:$PROXY_PORT" |
| #!/bin/bash | |
| NODE_NAME=$1 | |
| ROLLOUT_CMD=$2 | |
| if [[ "$NODE_NAME" == "" ]]; then | |
| echo " | |
| USAGE: ./drain.sh <NODE_NAME> | |
| Drains a node from its Deployments/Stateful set pods. |
