[ https://issues.jboss.org/browse/JBIDE-21700?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21700: --------------------------------------- Right now, relationships for this only can be walked from pod->rc(deployment)->dc via annotations pod: {{ "annotations": { "kubernetes.io/created-by": "{\"kind\":\"SerializedReference\",\"apiVersion\":\"v1\",\"reference\":{\"kind\":\"ReplicationController\",\"namespace\":\"hello-world\",\"name\":\"hello-openshift-2\",\"uid\":\"7b7dec8c-d4bf-11e5-b828-080027c5bfa9\",\"apiVersion\":\"v1\",\"resourceVersion\":\"41026\"}}\n", "openshift.io/deployment-config.latest-version": "2", "openshift.io/deployment-config.name": "hello-openshift", "openshift.io/deployment.name": "hello-openshift-2", "openshift.io/scc": "restricted" } }} rep controller: {{ "annotations": { "openshift.io/deployer-pod.name": "hello-openshift-2-deploy", "openshift.io/deployment-config.latest-version": "2", "openshift.io/deployment-config.name": "hello-openshift", "openshift.io/deployment.phase": "Complete", "openshift.io/deployment.replicas": "",}} We can either listen to the connection events directly, try to hook into the observable project cache, or try to write an event mechanism to encapsulate a deployment change to notify when the pod is available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)