apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:44:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-104-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-104.ec2.internal uid: c3e1d2bb-b006-4008-843a-ebaa88c8269e resourceVersion: "62299" uid: b60a7436-d57d-481b-a633-b2c5db8dcf92 spec: sourcePod: network-check-source-869dcfcdcd-n7rpt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T19:51:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.423896ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:26:08Z" - latency: 985.431µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:25:08Z" - latency: 1.218664ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:24:08Z" - latency: 1.055931ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:23:08Z" - latency: 1.346743ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:22:08Z" - latency: 952.728µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:21:08Z" - latency: 1.583242ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:20:08Z" - latency: 1.04121ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:19:08Z" - latency: 957.272µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:18:08Z" - latency: 934.739µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:17:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:44:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-104-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-104.ec2.internal uid: c3e1d2bb-b006-4008-843a-ebaa88c8269e resourceVersion: "62301" uid: 626e3581-f340-4899-b0ec-d7634004f8b7 spec: sourcePod: network-check-source-869dcfcdcd-n7rpt targetEndpoint: ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T19:50:08Z" message: 'load-balancer-api-external: tcp connection to ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.935499ms message: 'load-balancer-api-external: tcp connection to ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:26:08Z" - latency: 7.500608ms message: 'load-balancer-api-external: resolved host name ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:26:08Z" - latency: 5.227498ms message: 'load-balancer-api-external: tcp connection to ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:25:08Z" - latency: 7.439827ms message: 'load-balancer-api-external: resolved host name ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:25:08Z" - latency: 5.283624ms message: 'load-balancer-api-external: tcp connection to ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:24:08Z" - latency: 7.912401ms message: 'load-balancer-api-external: resolved host name ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:24:08Z" - latency: 4.409284ms message: 'load-balancer-api-external: tcp connection to ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:23:08Z" - latency: 7.338127ms message: 'load-balancer-api-external: resolved host name ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:23:08Z" - latency: 5.443251ms message: 'load-balancer-api-external: tcp connection to ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:22:08Z" - latency: 8.363275ms message: 'load-balancer-api-external: resolved host name ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:22:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:44:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-104-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-104.ec2.internal uid: c3e1d2bb-b006-4008-843a-ebaa88c8269e resourceVersion: "62300" uid: 2825db37-5747-4664-853e-36bc08bd7787 spec: sourcePod: network-check-source-869dcfcdcd-n7rpt targetEndpoint: ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T19:50:08Z" message: 'load-balancer-api-internal: tcp connection to ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.856798ms message: 'load-balancer-api-internal: tcp connection to ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:26:08Z" - latency: 7.423582ms message: 'load-balancer-api-internal: resolved host name ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:26:08Z" - latency: 4.967193ms message: 'load-balancer-api-internal: tcp connection to ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:25:08Z" - latency: 7.524255ms message: 'load-balancer-api-internal: resolved host name ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:25:08Z" - latency: 3.948788ms message: 'load-balancer-api-internal: tcp connection to ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:24:08Z" - latency: 7.874634ms message: 'load-balancer-api-internal: resolved host name ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:24:08Z" - latency: 3.644481ms message: 'load-balancer-api-internal: tcp connection to ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:23:08Z" - latency: 7.451067ms message: 'load-balancer-api-internal: resolved host name ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:23:08Z" - latency: 5.445364ms message: 'load-balancer-api-internal: tcp connection to ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:22:08Z" - latency: 8.347582ms message: 'load-balancer-api-internal: resolved host name ad134dda6e56b41218d007428edcb235-f1c5892064c860cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:22:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:44:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-104-to-network-check-target-ip-10-0-128-126 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-104.ec2.internal uid: c3e1d2bb-b006-4008-843a-ebaa88c8269e resourceVersion: "62298" uid: a87c0a78-c066-4a31-8dc0-bd0a2f07a11d spec: sourcePod: network-check-source-869dcfcdcd-n7rpt targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T19:51:08Z" message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.514738ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:26:08Z" - latency: 2.397849ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:25:08Z" - latency: 2.204877ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:24:08Z" - latency: 2.402832ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:23:08Z" - latency: 2.381358ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:22:08Z" - latency: 2.404468ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:21:08Z" - latency: 2.282071ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:20:08Z" - latency: 2.315436ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:19:08Z" - latency: 2.155961ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:18:08Z" - latency: 2.348818ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:17:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:44:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-104-to-network-check-target-ip-10-0-130-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-104.ec2.internal uid: c3e1d2bb-b006-4008-843a-ebaa88c8269e resourceVersion: "62295" uid: ee735562-2ac8-4ddd-b083-661a381e9149 spec: sourcePod: network-check-source-869dcfcdcd-n7rpt targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T19:51:08Z" message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.343847ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:26:08Z" - latency: 1.312392ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:25:08Z" - latency: 1.118472ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:24:08Z" - latency: 892.656µs message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:23:08Z" - latency: 1.191796ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:22:08Z" - latency: 1.084197ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:21:08Z" - latency: 1.254375ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:20:08Z" - latency: 887.041µs message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:19:08Z" - latency: 1.147364ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:18:08Z" - latency: 780.971µs message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:17:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:44:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-104-to-network-check-target-ip-10-0-136-12 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-104.ec2.internal uid: c3e1d2bb-b006-4008-843a-ebaa88c8269e resourceVersion: "62296" uid: 5f6534b9-a0a7-4572-a162-9209e1bc99a0 spec: sourcePod: network-check-source-869dcfcdcd-n7rpt targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T19:51:08Z" message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.930572ms message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:26:08Z" - latency: 2.044383ms message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:25:08Z" - latency: 1.840161ms message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:24:08Z" - latency: 1.915421ms message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:23:08Z" - latency: 1.864974ms message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:22:08Z" - latency: 1.78739ms message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:21:08Z" - latency: 2.005718ms message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:20:08Z" - latency: 1.91533ms message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:19:08Z" - latency: 2.158105ms message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:18:08Z" - latency: 1.895825ms message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:17:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:44:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-104-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-104.ec2.internal uid: c3e1d2bb-b006-4008-843a-ebaa88c8269e resourceVersion: "62297" uid: 757e0182-db29-473d-8aeb-5eebac6710ce spec: sourcePod: network-check-source-869dcfcdcd-n7rpt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T19:50:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 833.364µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:26:08Z" - latency: 1.789284ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T20:26:08Z" - latency: 1.049857ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:25:08Z" - latency: 1.997409ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T20:25:08Z" - latency: 830.604µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:24:08Z" - latency: 2.095484ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T20:24:08Z" - latency: 945.149µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:23:08Z" - latency: 1.788255ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T20:23:08Z" - latency: 892.783µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:22:08Z" - latency: 2.338454ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T20:22:08Z" kind: List metadata: resourceVersion: ""