application pod does not recreated when unidle svc on microshift

100%

1.Create project and test pods under it with rc and service and create a test pod as well say "hello-pod"
% oc create namespace test2
namespace/test2 created
% oc apply -f list-for-pods.json -n test2
replicationcontroller/test-rc created
service/test-service created
% oc apply -f pod.yaml -n test2
pod/hello-pod created
% oc get all -n test2
NAME                READY   STATUS    RESTARTS   AGE
pod/hello-pod       1/1     Running   0          16s
pod/test-rc-8mx8n   1/1     Running   0          34s
pod/test-rc-pgsf7   1/1     Running   0          34s


NAME                            DESIRED   CURRENT   READY   AGE
replicationcontroller/test-rc   2         2         2       34s


NAME                   TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)     AGE
service/test-service   ClusterIP   10.43.109.18   <none>        27017/TCP   34s

list-for-pods.json: https://raw.githubusercontent.com/anuragthehatter/v3-testfiles/master/networking/list_for_pods.json 
pod.yaml
---
apiVersion: v1
kind: Pod
metadata:
  name: hello-pod
spec:
  securityContext:
    runAsNonRoot: true
    seccompProfile:
      type: RuntimeDefault
  containers:
    - name: hello-pod
      image: "docker.io/ocpqe/hello-pod"

2.idle test-service, check application pods terminated
% oc idle test-service -n test2
The service "test2/test-service" has been marked as idled 
The service will unidle ReplicationController "test2/test-rc" to 2 replicas once it receives traffic 
ReplicationController "test2/test-rc" has been idled 
qiowang@qiowang-mac microshift % 
qiowang@qiowang-mac microshift % oc get all -owide -n test2   
NAME            READY   STATUS    RESTARTS   AGE   IP           NODE                                     NOMINATED NODE   READINESS GATES
pod/hello-pod   1/1     Running   0          14m   10.42.0.14   dhcp-1-235-246.arm.eng.rdu2.redhat.com   <none>           <none>


NAME                            DESIRED   CURRENT   READY   AGE   CONTAINERS   IMAGES               SELECTOR
replicationcontroller/test-rc   0         0         0       14m   test-pod     aosqe/pod-for-ping   name=test-pods


NAME                   TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)     AGE   SELECTOR
service/test-service   ClusterIP   10.43.109.18   <none>        27017/TCP   14m   name=test-pods

3.Now from the test pod "hello-pod", curl to the service ip
% oc rsh -n test2 hello-pod 
sh-4.2$ curl 10.43.109.18:27017
curl: (7) Failed connect to 10.43.109.18:27017; Connection refused

4. Check the pods again and make sure they are being recreated due to unidling of svc
% oc get pods -n test2
NAME        READY   STATUS    RESTARTS   AGE
hello-pod   1/1     Running   0          49m

sh-4.2$ curl 10.43.109.18:27017
curl: (7) Failed connect to 10.43.109.18:27017; Connection refused

application pod does not recreated 

sh-4.2$ curl 10.43.109.18:27017
Hello OpenShift!

application pods are being recreated due to unidling of svc