A legacy municipal UI keeps server-side session state in memory on one Pod. Which Service setting improves sticky routing by client IP?
Select an answer to reveal the explanation.
Short Explanation
Sticky sessions are like always sending a citizen back to the same clerk window. sessionAffinity: ClientIP tells the Service to prefer the same backend for that client IP. It’s a band-aid for sticky legacy UIs—not a reason to skip proper shared session stores forever.
Full Explanation
Service sessionAffinity: ClientIP attempts to send requests from the same client IP to the same backend Pod. That can help legacy apps with in-memory sessions. publishNotReadyAddresses controls whether not-ready Pods appear in Endpoints, ExternalName does not provide Pod session stickiness, and deleting Endpoints is not a stickiness mechanism.