Kong Ingress not working after pod restart

Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4", GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"clean", BuildDate:"2021-11-17T15:48:33Z", GoVersion:"go1.16.10", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.1", GitCommit:"206bcadf021e76c27513500ca24182692aabd17e", GitTreeState:"clean", BuildDate:"2020-09-09T11:18:22Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}

Hi, I’m using Kong Ingress Controller & Proxy on my edge node in K8s , which in centos 7, I found out that when the pod is evicted / create after deletion, although the pod is successfully running, but it doesn’t work. But after i restart the worker node and create the pod again, it works. My expected scenario should be: even the pod is evicted/ create after deletion, it does not require any reboot of machine to make the thing work. Any thing I should config in order to avoid such situation?

Kong Ingress Controller Version : 0.8
Kong version : 2.1.3