apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T04:12:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-226-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-226.ec2.internal uid: eac15264-7201-42ae-a744-569b7f8b6ede resourceVersion: "62948" uid: 9bb96df7-ac14-4f4a-9942-8b2bb74cf598 spec: sourcePod: network-check-source-7bc5b6bf85-ln2tp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-21T04:19:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.012806ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:54:30Z" - latency: 1.278617ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:53:30Z" - latency: 1.241509ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:52:30Z" - latency: 788.855µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:51:30Z" - latency: 746.875µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:50:30Z" - latency: 1.324602ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:49:30Z" - latency: 974.22µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:48:30Z" - latency: 896.671µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:47:30Z" - latency: 992.259µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:46:30Z" - latency: 1.018604ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:45:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T04:12:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-226-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-226.ec2.internal uid: eac15264-7201-42ae-a744-569b7f8b6ede resourceVersion: "62949" uid: 94bb3716-a339-4dc5-9970-5d3d2db7aeb9 spec: sourcePod: network-check-source-7bc5b6bf85-ln2tp targetEndpoint: abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T04:18:31Z" message: 'load-balancer-api-external: tcp connection to abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.49737ms message: 'load-balancer-api-external: tcp connection to abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:54:30Z" - latency: 6.680375ms message: 'load-balancer-api-external: resolved host name abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:54:30Z" - latency: 3.802591ms message: 'load-balancer-api-external: tcp connection to abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:53:30Z" - latency: 6.437932ms message: 'load-balancer-api-external: resolved host name abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:53:30Z" - latency: 4.405823ms message: 'load-balancer-api-external: tcp connection to abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:52:30Z" - latency: 6.940444ms message: 'load-balancer-api-external: resolved host name abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:52:30Z" - latency: 4.726964ms message: 'load-balancer-api-external: tcp connection to abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:51:30Z" - latency: 7.687052ms message: 'load-balancer-api-external: resolved host name abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:51:30Z" - latency: 4.201547ms message: 'load-balancer-api-external: tcp connection to abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:50:30Z" - latency: 6.619961ms message: 'load-balancer-api-external: resolved host name abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:50:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T04:12:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-226-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-226.ec2.internal uid: eac15264-7201-42ae-a744-569b7f8b6ede resourceVersion: "62951" uid: fa310fdc-ebf9-4112-b8b5-f05be96c05c3 spec: sourcePod: network-check-source-7bc5b6bf85-ln2tp targetEndpoint: abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T04:18:31Z" message: 'load-balancer-api-internal: tcp connection to abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.357834ms message: 'load-balancer-api-internal: tcp connection to abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:54:30Z" - latency: 6.806191ms message: 'load-balancer-api-internal: resolved host name abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:54:30Z" - latency: 3.82822ms message: 'load-balancer-api-internal: tcp connection to abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:53:30Z" - latency: 6.467832ms message: 'load-balancer-api-internal: resolved host name abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:53:30Z" - latency: 4.558222ms message: 'load-balancer-api-internal: tcp connection to abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:52:30Z" - latency: 7.02292ms message: 'load-balancer-api-internal: resolved host name abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:52:30Z" - latency: 4.657418ms message: 'load-balancer-api-internal: tcp connection to abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:51:30Z" - latency: 7.77959ms message: 'load-balancer-api-internal: resolved host name abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:51:30Z" - latency: 4.192192ms message: 'load-balancer-api-internal: tcp connection to abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:50:30Z" - latency: 6.668888ms message: 'load-balancer-api-internal: resolved host name abb726dee424e49a68b461daa8ee69e7-45561affb1b1b8a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:50:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T04:12:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-226-to-network-check-target-ip-10-0-134-95 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-226.ec2.internal uid: eac15264-7201-42ae-a744-569b7f8b6ede resourceVersion: "62945" uid: 460356b1-bd9a-4d44-8498-4065a3fbd72a spec: sourcePod: network-check-source-7bc5b6bf85-ln2tp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T04:19:30Z" message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.18517ms message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:54:30Z" - latency: 2.036718ms message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:53:30Z" - latency: 2.192205ms message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:52:30Z" - latency: 2.050084ms message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:51:30Z" - latency: 2.055173ms message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:50:30Z" - latency: 2.320111ms message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:49:30Z" - latency: 2.258731ms message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:48:30Z" - latency: 2.390354ms message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:47:30Z" - latency: 2.395299ms message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:46:30Z" - latency: 2.421008ms message: 'network-check-target-ip-10-0-134-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:45:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T04:12:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-226-to-network-check-target-ip-10-0-137-226 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-226.ec2.internal uid: eac15264-7201-42ae-a744-569b7f8b6ede resourceVersion: "62944" uid: aa69ad8c-3532-4d27-8177-98a1533afcdb spec: sourcePod: network-check-source-7bc5b6bf85-ln2tp targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-21T04:19:30Z" message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.415929ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:54:30Z" - latency: 853.485µs message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:53:30Z" - latency: 989.817µs message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:52:30Z" - latency: 781.645µs message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:51:30Z" - latency: 1.022928ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:50:30Z" - latency: 1.501565ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:49:30Z" - latency: 1.079544ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:48:30Z" - latency: 814.319µs message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:47:30Z" - latency: 896.256µs message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:46:30Z" - latency: 1.34565ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:45:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T04:12:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-226-to-network-check-target-ip-10-0-140-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-226.ec2.internal uid: eac15264-7201-42ae-a744-569b7f8b6ede resourceVersion: "62946" uid: 04ea337d-246e-4ee8-b1af-d424a905bec2 spec: sourcePod: network-check-source-7bc5b6bf85-ln2tp targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-21T04:19:30Z" message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.984667ms message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:54:30Z" - latency: 2.066924ms message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:53:30Z" - latency: 2.117118ms message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:52:30Z" - latency: 1.690187ms message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:51:30Z" - latency: 1.903848ms message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:50:30Z" - latency: 2.091217ms message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:49:30Z" - latency: 1.936184ms message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:48:30Z" - latency: 2.119151ms message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:47:30Z" - latency: 2.331169ms message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:46:30Z" - latency: 1.79626ms message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:45:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T04:12:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-226-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-226.ec2.internal uid: eac15264-7201-42ae-a744-569b7f8b6ede resourceVersion: "62947" uid: 71a907b1-52f8-4e6b-bf4e-59c7724a8df1 spec: sourcePod: network-check-source-7bc5b6bf85-ln2tp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-21T04:18:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.352174ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:54:30Z" - latency: 1.732388ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T04:54:30Z" - latency: 957.324µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:53:30Z" - latency: 1.654788ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T04:53:30Z" - latency: 913.925µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:52:30Z" - latency: 1.878055ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T04:52:30Z" - latency: 1.035238ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:51:30Z" - latency: 2.420434ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T04:51:30Z" - latency: 918.115µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:50:30Z" - latency: 1.718339ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T04:50:30Z" kind: List metadata: resourceVersion: ""