pod is not changing state from unready to ready

Question

I am using the readiness probe feature in my k8s pod. For this, probe checks if the file /tmp/healthy is present or not. If not, probe mark pod UN-READY. I have observed If I create the file again /tmp/healthy, the pod does not come back to READY state. Does it mean, in pod lifecycle there is only path of READY--> UN-READY but not vice-versa?

/home/ravi/for_others/ric/stub>kubectl describe pod -n myns  deployment-eterm
Name:         deployment-eterm
Namespace:    myns
Priority:     0
Status:       Running
IP:           192.168.252.87
IPs:
  IP:           192.168.252.87
Controlled By:  ReplicaSet/deployment-myns-eterm-micro-6b896556c8
Containers:
    Liveness:       exec [/bin/sh -c /tmp/liveliness-status-collector.sh] delay=60s timeout=1s period=2s #success=1 #failure=5
    Readiness:      exec [/bin/sh -c cat /tmp/healthy] delay=60s timeout=1s period=10s #success=1 #failure=1
    Environment Variables from:
      configmap-myns-eterm-env-micro  ConfigMap  Optional: false
    Environment:                       <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-57jpz (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason     Age               From                    Message
  ----     ------     ----              ----                    -------
  Normal   Scheduled  9m11s             default-scheduler       Successfully assigned myns/deployment-eterm to mnode
  Normal   Pulled     9m10s             kubelet, mnode  Container image "porics.microlab.com:5000/eterm:latest" already present on machine
  Normal   Created    9m10s             kubelet, mnode  Created container container-myns-eterm
  Normal   Started    9m10s             kubelet, mnode  Started container container-myns-eterm
  Normal   Pulled     9m10s             kubelet, mnode  Container image "porics.microlab.com:5000/config-proxy:latest" already present on machine
  Normal   Created    9m10s             kubelet, mnode  Created container container-myns-configproxy
  Normal   Started    9m10s             kubelet, mnode  Started container container-myns-configproxy
  Warning  Unhealthy  3s (x3 over 23s)  kubelet, mnode  Readiness probe failed: cat: /tmp/healthy: No such file or directory
/home/ravi/for_others/ric/stub>

Answer 1

Try

=importxml(url,"//div[@id='nav-subnav']/@data-category")

or

=index(importxml(url,"//div[@id='nav-subnav']"),1)