Hi Team , we are facing issue with the kong sticky session .
setup : kong running on kubernetes and upstream application also runs on kubernetes in different namespaces
kong accessible via node port and application accessible via clusterip
so have few questions
1.is kong pod make session to application pod or to application service endpoint
2. is keep alive timeout in kong control the dns refresh interval at kong
kong establish session with application , but when application pod are deleted , kong does not refresh itself and still refers to the old ip of application pod .
workaround that we see is to restart kong pod that correct the entries in kong
so does any one faced similar issue