apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T16:20:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-40-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-40.ec2.internal uid: 72836bf0-de32-4ad4-8ffa-c488336c0430 resourceVersion: "58298" uid: 68ecab68-e017-4f28-831e-ccb8903b1775 spec: sourcePod: network-check-source-685456655f-mqnrc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-10T16:27:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.226023ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:48:15Z" - latency: 880.469µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:47:15Z" - latency: 975.61µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:46:15Z" - latency: 1.233489ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:45:15Z" - latency: 1.386638ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:44:15Z" - latency: 1.376871ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:43:15Z" - latency: 1.066019ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:42:15Z" - latency: 952.797µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:41:15Z" - latency: 1.309554ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:40:15Z" - latency: 1.043104ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:39:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T16:20:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-40-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-40.ec2.internal uid: 72836bf0-de32-4ad4-8ffa-c488336c0430 resourceVersion: "59956" uid: 01ff02f9-c8ec-489f-92c7-e25320938b47 spec: sourcePod: network-check-source-685456655f-mqnrc targetEndpoint: a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T16:26:15Z" message: 'load-balancer-api-external: tcp connection to a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.690032ms message: 'load-balancer-api-external: tcp connection to a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:50:15Z" - latency: 8.668983ms message: 'load-balancer-api-external: resolved host name a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:50:15Z" - latency: 5.74908ms message: 'load-balancer-api-external: tcp connection to a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:49:15Z" - latency: 9.20432ms message: 'load-balancer-api-external: resolved host name a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:49:15Z" - latency: 3.866107ms message: 'load-balancer-api-external: tcp connection to a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:48:15Z" - latency: 10.176608ms message: 'load-balancer-api-external: resolved host name a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:48:15Z" - latency: 3.711851ms message: 'load-balancer-api-external: tcp connection to a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:47:15Z" - latency: 8.73558ms message: 'load-balancer-api-external: resolved host name a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:47:15Z" - latency: 5.301531ms message: 'load-balancer-api-external: tcp connection to a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:46:15Z" - latency: 8.578079ms message: 'load-balancer-api-external: resolved host name a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:46:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T16:20:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-40-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-40.ec2.internal uid: 72836bf0-de32-4ad4-8ffa-c488336c0430 resourceVersion: "59957" uid: e669f193-277a-47f9-be2e-08ad04fa6f84 spec: sourcePod: network-check-source-685456655f-mqnrc targetEndpoint: a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T16:26:15Z" message: 'load-balancer-api-internal: tcp connection to a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.723126ms message: 'load-balancer-api-internal: tcp connection to a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:50:15Z" - latency: 8.570861ms message: 'load-balancer-api-internal: resolved host name a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:50:15Z" - latency: 5.511094ms message: 'load-balancer-api-internal: tcp connection to a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:49:15Z" - latency: 9.129904ms message: 'load-balancer-api-internal: resolved host name a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:49:15Z" - latency: 4.771463ms message: 'load-balancer-api-internal: tcp connection to a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:48:15Z" - latency: 10.121946ms message: 'load-balancer-api-internal: resolved host name a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:48:15Z" - latency: 4.433359ms message: 'load-balancer-api-internal: tcp connection to a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:47:15Z" - latency: 8.764545ms message: 'load-balancer-api-internal: resolved host name a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:47:15Z" - latency: 5.332298ms message: 'load-balancer-api-internal: tcp connection to a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:46:15Z" - latency: 8.50393ms message: 'load-balancer-api-internal: resolved host name a5c1b4c54df224587b73eb5af815efe6-40d2fb5638987860.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:46:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T16:20:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-40-to-network-check-target-ip-10-0-136-40 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-40.ec2.internal uid: 72836bf0-de32-4ad4-8ffa-c488336c0430 resourceVersion: "58295" uid: 7dd0e9c9-15d9-4d07-aed3-1fdaabdd6ca7 spec: sourcePod: network-check-source-685456655f-mqnrc targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-10T16:27:15Z" message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 946.944µs message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:48:15Z" - latency: 1.136277ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:47:15Z" - latency: 1.647122ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:46:15Z" - latency: 1.044047ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:45:15Z" - latency: 1.710597ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:44:15Z" - latency: 947.221µs message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:43:15Z" - latency: 1.25954ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:42:15Z" - latency: 1.371389ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:41:15Z" - latency: 1.62864ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:40:15Z" - latency: 1.110648ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:39:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T16:20:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-40-to-network-check-target-ip-10-0-138-74 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-40.ec2.internal uid: 72836bf0-de32-4ad4-8ffa-c488336c0430 resourceVersion: "58297" uid: a3b0de36-3051-448d-a9e7-92d0c0790197 spec: sourcePod: network-check-source-685456655f-mqnrc targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-10T16:27:15Z" message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.475249ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:48:15Z" - latency: 2.4186ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:47:15Z" - latency: 2.57569ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:46:15Z" - latency: 2.460615ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:45:15Z" - latency: 2.339376ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:44:15Z" - latency: 2.366116ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:43:15Z" - latency: 2.287876ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:42:15Z" - latency: 2.225545ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:41:15Z" - latency: 2.373071ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:40:15Z" - latency: 2.37322ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:39:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T16:20:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-40-to-network-check-target-ip-10-0-139-24 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-40.ec2.internal uid: 72836bf0-de32-4ad4-8ffa-c488336c0430 resourceVersion: "58296" uid: e2b45550-af1a-4674-b364-3d6cf46077dc spec: sourcePod: network-check-source-685456655f-mqnrc targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-10T16:27:15Z" message: 'network-check-target-ip-10-0-139-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.168337ms message: 'network-check-target-ip-10-0-139-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:48:15Z" - latency: 1.946211ms message: 'network-check-target-ip-10-0-139-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:47:15Z" - latency: 2.045379ms message: 'network-check-target-ip-10-0-139-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:46:15Z" - latency: 2.23647ms message: 'network-check-target-ip-10-0-139-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:45:15Z" - latency: 1.867634ms message: 'network-check-target-ip-10-0-139-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:44:15Z" - latency: 2.299154ms message: 'network-check-target-ip-10-0-139-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:43:15Z" - latency: 2.141593ms message: 'network-check-target-ip-10-0-139-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:42:15Z" - latency: 2.04576ms message: 'network-check-target-ip-10-0-139-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:41:15Z" - latency: 2.359251ms message: 'network-check-target-ip-10-0-139-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:40:15Z" - latency: 2.049539ms message: 'network-check-target-ip-10-0-139-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:39:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T16:20:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-40-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-40.ec2.internal uid: 72836bf0-de32-4ad4-8ffa-c488336c0430 resourceVersion: "59954" uid: 85d0fc6e-fddb-4732-8741-519743fb28f0 spec: sourcePod: network-check-source-685456655f-mqnrc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-10T16:26:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.105743ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:50:15Z" - latency: 1.900451ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T16:50:15Z" - latency: 996.376µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:49:15Z" - latency: 1.892182ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T16:49:15Z" - latency: 1.389036ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:48:15Z" - latency: 1.907013ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T16:48:15Z" - latency: 941.78µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:47:15Z" - latency: 2.017956ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T16:47:15Z" - latency: 822.487µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:46:15Z" - latency: 1.999723ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T16:46:15Z" kind: List metadata: resourceVersion: ""