apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:36:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-182-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-182.ec2.internal uid: 31bff796-71b5-4797-9950-542ec4bac53e resourceVersion: "39507" uid: 4f4038f5-51af-4928-aac2-fa96baed16a9 spec: sourcePod: network-check-source-8894fc9bd-2nzr7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T16:43:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 958.266µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:32:07Z" - latency: 1.009421ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:31:07Z" - latency: 819.828µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:30:07Z" - latency: 848.819µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:29:07Z" - latency: 1.007599ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:28:07Z" - latency: 910.377µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:27:07Z" - latency: 1.298404ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:26:07Z" - latency: 873.971µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:25:07Z" - latency: 1.245192ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:24:07Z" - latency: 893.835µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:23:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:36:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-182-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-182.ec2.internal uid: 31bff796-71b5-4797-9950-542ec4bac53e resourceVersion: "41585" uid: 1c51a66f-2fa0-4c2a-b881-952ffd4e0686 spec: sourcePod: network-check-source-8894fc9bd-2nzr7 targetEndpoint: abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T16:42:07Z" message: 'load-balancer-api-external: tcp connection to abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.4321ms message: 'load-balancer-api-external: tcp connection to abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:36:07Z" - latency: 14.522592ms message: 'load-balancer-api-external: resolved host name abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:36:07Z" - latency: 4.023189ms message: 'load-balancer-api-external: tcp connection to abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:35:07Z" - latency: 7.930871ms message: 'load-balancer-api-external: resolved host name abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:35:07Z" - latency: 4.29057ms message: 'load-balancer-api-external: tcp connection to abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:34:07Z" - latency: 8.212911ms message: 'load-balancer-api-external: resolved host name abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:34:07Z" - latency: 5.846452ms message: 'load-balancer-api-external: tcp connection to abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:33:07Z" - latency: 18.54956ms message: 'load-balancer-api-external: resolved host name abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:33:07Z" - latency: 5.329329ms message: 'load-balancer-api-external: tcp connection to abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:32:07Z" - latency: 13.628402ms message: 'load-balancer-api-external: resolved host name abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:32:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:36:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-182-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-182.ec2.internal uid: 31bff796-71b5-4797-9950-542ec4bac53e resourceVersion: "41586" uid: 468e4799-43f1-4a4c-99b2-c653c96f7070 spec: sourcePod: network-check-source-8894fc9bd-2nzr7 targetEndpoint: abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T16:42:07Z" message: 'load-balancer-api-internal: tcp connection to abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.449871ms message: 'load-balancer-api-internal: tcp connection to abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:36:07Z" - latency: 14.446754ms message: 'load-balancer-api-internal: resolved host name abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:36:07Z" - latency: 4.008474ms message: 'load-balancer-api-internal: tcp connection to abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:35:07Z" - latency: 7.863265ms message: 'load-balancer-api-internal: resolved host name abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:35:07Z" - latency: 4.276253ms message: 'load-balancer-api-internal: tcp connection to abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:34:07Z" - latency: 8.191396ms message: 'load-balancer-api-internal: resolved host name abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:34:07Z" - latency: 5.885375ms message: 'load-balancer-api-internal: tcp connection to abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:33:07Z" - latency: 18.505029ms message: 'load-balancer-api-internal: resolved host name abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:33:07Z" - latency: 5.318604ms message: 'load-balancer-api-internal: tcp connection to abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:32:07Z" - latency: 13.655904ms message: 'load-balancer-api-internal: resolved host name abff99fd067734066b555a738e1885e1-da717e0a41fe01e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:32:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:36:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-182-to-network-check-target-ip-10-0-128-217 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-182.ec2.internal uid: 31bff796-71b5-4797-9950-542ec4bac53e resourceVersion: "39505" uid: c76d875c-ad6f-49fa-bc2f-d767187aec71 spec: sourcePod: network-check-source-8894fc9bd-2nzr7 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T16:43:07Z" message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.433214ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:32:07Z" - latency: 2.361754ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:31:07Z" - latency: 2.325463ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:30:07Z" - latency: 2.11353ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:29:07Z" - latency: 2.310021ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:28:07Z" - latency: 2.326956ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:27:07Z" - latency: 2.420845ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:26:07Z" - latency: 1.960243ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:25:07Z" - latency: 2.350684ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:24:07Z" - latency: 2.215325ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:23:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:36:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-182-to-network-check-target-ip-10-0-136-182 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-182.ec2.internal uid: 31bff796-71b5-4797-9950-542ec4bac53e resourceVersion: "39504" uid: 105e083f-d3ff-45ca-96be-8ac09d64a335 spec: sourcePod: network-check-source-8894fc9bd-2nzr7 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-17T16:43:07Z" message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 853.722µs message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:32:07Z" - latency: 847.195µs message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:31:07Z" - latency: 797.83µs message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:30:07Z" - latency: 738.713µs message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:29:07Z" - latency: 909.195µs message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:28:07Z" - latency: 1.018042ms message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:27:07Z" - latency: 795.851µs message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:26:07Z" - latency: 814.016µs message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:25:07Z" - latency: 809.479µs message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:24:07Z" - latency: 885.548µs message: 'network-check-target-ip-10-0-136-182: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:23:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:36:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-182-to-network-check-target-ip-10-0-141-140 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-182.ec2.internal uid: 31bff796-71b5-4797-9950-542ec4bac53e resourceVersion: "39506" uid: 3aa93fb6-14cb-499e-bdda-c3b80b10b41a spec: sourcePod: network-check-source-8894fc9bd-2nzr7 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-17T16:43:07Z" message: 'network-check-target-ip-10-0-141-140: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.405708ms message: 'network-check-target-ip-10-0-141-140: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:32:07Z" - latency: 2.360469ms message: 'network-check-target-ip-10-0-141-140: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:31:07Z" - latency: 2.266185ms message: 'network-check-target-ip-10-0-141-140: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:30:07Z" - latency: 1.951873ms message: 'network-check-target-ip-10-0-141-140: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:29:07Z" - latency: 2.26081ms message: 'network-check-target-ip-10-0-141-140: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:28:07Z" - latency: 2.084313ms message: 'network-check-target-ip-10-0-141-140: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:27:07Z" - latency: 2.345976ms message: 'network-check-target-ip-10-0-141-140: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:26:07Z" - latency: 2.374791ms message: 'network-check-target-ip-10-0-141-140: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:25:07Z" - latency: 2.565292ms message: 'network-check-target-ip-10-0-141-140: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:24:07Z" - latency: 2.692168ms message: 'network-check-target-ip-10-0-141-140: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:23:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:36:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-182-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-182.ec2.internal uid: 31bff796-71b5-4797-9950-542ec4bac53e resourceVersion: "41583" uid: ec1724c5-2f38-41c6-bedc-1a3d92049941 spec: sourcePod: network-check-source-8894fc9bd-2nzr7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T16:42:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 769.714µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:36:07Z" - latency: 1.404661ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:36:07Z" - latency: 746.334µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:35:07Z" - latency: 1.506544ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:35:07Z" - latency: 730.197µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:34:07Z" - latency: 1.887251ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:34:07Z" - latency: 859.197µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:33:07Z" - latency: 1.812772ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:33:07Z" - latency: 860.744µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:32:07Z" - latency: 1.770011ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:32:07Z" kind: List metadata: resourceVersion: ""