apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T10:30:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-90-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-90.us-east-2.compute.internal uid: eb808f84-1323-4221-b428-e3031330209d resourceVersion: "210427" uid: 90bdbf03-5fdc-4574-a997-b747416426a2 spec: sourcePod: network-check-source-6f78d59f99-wkrtf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T10:37:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.30276ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:33:57Z" - latency: 1.20247ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:32:57Z" - latency: 879.572µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:31:57Z" - latency: 1.477433ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:30:57Z" - latency: 1.45164ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:29:57Z" - latency: 1.562456ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:28:57Z" - latency: 1.706919ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:27:57Z" - latency: 1.154278ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:26:57Z" - latency: 1.408128ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:25:57Z" - latency: 2.065512ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:24:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T10:30:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-90-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-90.us-east-2.compute.internal uid: eb808f84-1323-4221-b428-e3031330209d resourceVersion: "199488" uid: 39f21eef-3e59-4066-96e0-3726cc5855d6 spec: sourcePod: network-check-source-6f78d59f99-wkrtf targetEndpoint: a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T10:36:57Z" message: 'load-balancer-api-external: tcp connection to a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.063778ms message: 'load-balancer-api-external: tcp connection to a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:30:57Z" - latency: 8.170375ms message: 'load-balancer-api-external: resolved host name a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T11:30:57Z" - latency: 6.042813ms message: 'load-balancer-api-external: tcp connection to a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:29:57Z" - latency: 6.438111ms message: 'load-balancer-api-external: resolved host name a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T11:29:57Z" - latency: 5.373669ms message: 'load-balancer-api-external: tcp connection to a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:28:57Z" - latency: 9.505499ms message: 'load-balancer-api-external: resolved host name a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T11:28:57Z" - latency: 5.312329ms message: 'load-balancer-api-external: tcp connection to a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:27:57Z" - latency: 7.601138ms message: 'load-balancer-api-external: resolved host name a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T11:27:57Z" - latency: 4.85667ms message: 'load-balancer-api-external: tcp connection to a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:26:57Z" - latency: 7.991838ms message: 'load-balancer-api-external: resolved host name a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T11:26:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T10:30:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-90-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-90.us-east-2.compute.internal uid: eb808f84-1323-4221-b428-e3031330209d resourceVersion: "199487" uid: 798904bc-9cc9-42ee-b31c-4a34e02bef51 spec: sourcePod: network-check-source-6f78d59f99-wkrtf targetEndpoint: a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T10:36:57Z" message: 'load-balancer-api-internal: tcp connection to a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.072234ms message: 'load-balancer-api-internal: tcp connection to a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:30:57Z" - latency: 8.111156ms message: 'load-balancer-api-internal: resolved host name a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T11:30:57Z" - latency: 6.057277ms message: 'load-balancer-api-internal: tcp connection to a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:29:57Z" - latency: 6.324755ms message: 'load-balancer-api-internal: resolved host name a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T11:29:57Z" - latency: 5.391392ms message: 'load-balancer-api-internal: tcp connection to a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:28:57Z" - latency: 9.424831ms message: 'load-balancer-api-internal: resolved host name a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T11:28:57Z" - latency: 5.308593ms message: 'load-balancer-api-internal: tcp connection to a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:27:57Z" - latency: 7.537793ms message: 'load-balancer-api-internal: resolved host name a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T11:27:57Z" - latency: 4.86783ms message: 'load-balancer-api-internal: tcp connection to a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:26:57Z" - latency: 7.91759ms message: 'load-balancer-api-internal: resolved host name a49f260770125401da225bd50de2d2ed-cb79239a13837873.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T11:26:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T10:30:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-90-to-network-check-target-ip-10-0-134-12 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-90.us-east-2.compute.internal uid: eb808f84-1323-4221-b428-e3031330209d resourceVersion: "210425" uid: 810a10be-d41c-4a9a-b3ae-13f3d26bd2a2 spec: sourcePod: network-check-source-6f78d59f99-wkrtf targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T10:37:57Z" message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.597468ms message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:33:57Z" - latency: 2.02763ms message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:32:57Z" - latency: 2.380848ms message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:31:57Z" - latency: 2.323499ms message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:30:57Z" - latency: 2.570253ms message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:29:57Z" - latency: 2.312319ms message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:28:57Z" - latency: 3.382887ms message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:27:57Z" - latency: 2.223064ms message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:26:57Z" - latency: 2.358097ms message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:25:57Z" - latency: 2.957478ms message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:24:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T10:30:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-90-to-network-check-target-ip-10-0-138-233 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-90.us-east-2.compute.internal uid: eb808f84-1323-4221-b428-e3031330209d resourceVersion: "210426" uid: 04548548-a93c-4ca7-bb91-3b94f47536ae spec: sourcePod: network-check-source-6f78d59f99-wkrtf targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T10:37:57Z" message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.158756ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:33:57Z" - latency: 2.594415ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:32:57Z" - latency: 2.863616ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:31:57Z" - latency: 2.745992ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:30:57Z" - latency: 2.772263ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:29:57Z" - latency: 2.492766ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:28:57Z" - latency: 2.507015ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:27:57Z" - latency: 2.507993ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:26:57Z" - latency: 11.239ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:25:57Z" - latency: 4.649476ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:24:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T10:30:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-90-to-network-check-target-ip-10-0-139-90 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-90.us-east-2.compute.internal uid: eb808f84-1323-4221-b428-e3031330209d resourceVersion: "210424" uid: cbbf4b35-a2f9-401a-b143-cafa59d3ea76 spec: sourcePod: network-check-source-6f78d59f99-wkrtf targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T10:37:57Z" message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 997.059µs message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:33:57Z" - latency: 1.02911ms message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:32:57Z" - latency: 1.327643ms message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:31:57Z" - latency: 998.631µs message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:30:57Z" - latency: 1.017874ms message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:29:57Z" - latency: 1.849291ms message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:28:57Z" - latency: 1.195889ms message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:27:57Z" - latency: 1.119417ms message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:26:57Z" - latency: 1.399115ms message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:25:57Z" - latency: 1.849741ms message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:24:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T10:30:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-90-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-90.us-east-2.compute.internal uid: eb808f84-1323-4221-b428-e3031330209d resourceVersion: "199485" uid: d2da31ef-d44a-42d0-8ff3-59f0b0e7b16b spec: sourcePod: network-check-source-6f78d59f99-wkrtf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T10:36:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.072638ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:30:57Z" - latency: 2.273785ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T11:30:57Z" - latency: 988.051µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:29:57Z" - latency: 2.105597ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T11:29:57Z" - latency: 1.329948ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:28:57Z" - latency: 2.057023ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T11:28:57Z" - latency: 1.286912ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:27:57Z" - latency: 2.139768ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T11:27:57Z" - latency: 1.331341ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T11:26:57Z" - latency: 2.332013ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T11:26:57Z" kind: List metadata: resourceVersion: ""