apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T01:51:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-48-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-48.ec2.internal uid: 67d8d4c1-6d5d-4629-b927-577243a38576 resourceVersion: "56481" uid: abfa3eb9-b126-4a2a-bc5a-f0c64f4de741 spec: sourcePod: network-check-source-7bc5b6bf85-srh28 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-18T01:58:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.078323ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:26:42Z" - latency: 1.159054ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:25:42Z" - latency: 1.199853ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:24:42Z" - latency: 989.154µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:23:42Z" - latency: 1.352241ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:22:42Z" - latency: 1.09767ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:21:42Z" - latency: 935.495µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:20:42Z" - latency: 1.051155ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:19:42Z" - latency: 1.495987ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:18:42Z" - latency: 1.278995ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:17:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T01:51:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-48-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-48.ec2.internal uid: 67d8d4c1-6d5d-4629-b927-577243a38576 resourceVersion: "57625" uid: efa3ab84-c20f-449b-a584-c8e63b78ea15 spec: sourcePod: network-check-source-7bc5b6bf85-srh28 targetEndpoint: ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-18T01:57:42Z" message: 'load-balancer-api-external: tcp connection to ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.204428ms message: 'load-balancer-api-external: tcp connection to ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:27:42Z" - latency: 9.393291ms message: 'load-balancer-api-external: resolved host name ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:27:42Z" - latency: 3.487758ms message: 'load-balancer-api-external: tcp connection to ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:26:42Z" - latency: 8.788167ms message: 'load-balancer-api-external: resolved host name ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:26:42Z" - latency: 4.40227ms message: 'load-balancer-api-external: tcp connection to ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:25:42Z" - latency: 9.796552ms message: 'load-balancer-api-external: resolved host name ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:25:42Z" - latency: 4.453844ms message: 'load-balancer-api-external: tcp connection to ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:24:42Z" - latency: 9.033793ms message: 'load-balancer-api-external: resolved host name ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:24:42Z" - latency: 4.705483ms message: 'load-balancer-api-external: tcp connection to ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:23:42Z" - latency: 8.633053ms message: 'load-balancer-api-external: resolved host name ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:23:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T01:51:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-48-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-48.ec2.internal uid: 67d8d4c1-6d5d-4629-b927-577243a38576 resourceVersion: "57626" uid: 2d453935-5d64-4adc-aa20-d305f233c8a3 spec: sourcePod: network-check-source-7bc5b6bf85-srh28 targetEndpoint: ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-18T01:57:42Z" message: 'load-balancer-api-internal: tcp connection to ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.953651ms message: 'load-balancer-api-internal: tcp connection to ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:27:42Z" - latency: 9.424108ms message: 'load-balancer-api-internal: resolved host name ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:27:42Z" - latency: 3.471462ms message: 'load-balancer-api-internal: tcp connection to ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:26:42Z" - latency: 8.890027ms message: 'load-balancer-api-internal: resolved host name ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:26:42Z" - latency: 4.367661ms message: 'load-balancer-api-internal: tcp connection to ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:25:42Z" - latency: 9.836552ms message: 'load-balancer-api-internal: resolved host name ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:25:42Z" - latency: 4.486334ms message: 'load-balancer-api-internal: tcp connection to ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:24:42Z" - latency: 8.999411ms message: 'load-balancer-api-internal: resolved host name ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:24:42Z" - latency: 4.805885ms message: 'load-balancer-api-internal: tcp connection to ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:23:42Z" - latency: 8.624974ms message: 'load-balancer-api-internal: resolved host name ab5dd6c740576470cbdc264a39be342e-d28bb3d4cc18d64f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:23:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T01:51:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-48-to-network-check-target-ip-10-0-128-229 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-48.ec2.internal uid: 67d8d4c1-6d5d-4629-b927-577243a38576 resourceVersion: "56479" uid: 0c1f072f-9818-46b1-93a1-759858b7c845 spec: sourcePod: network-check-source-7bc5b6bf85-srh28 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-18T01:58:42Z" message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.430437ms message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:26:42Z" - latency: 2.434435ms message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:25:42Z" - latency: 2.234765ms message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:24:42Z" - latency: 2.223753ms message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:23:42Z" - latency: 1.99596ms message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:22:42Z" - latency: 1.982764ms message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:21:42Z" - latency: 2.265938ms message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:20:42Z" - latency: 2.043425ms message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:19:42Z" - latency: 2.398904ms message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:18:42Z" - latency: 2.321678ms message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:17:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T01:51:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-48-to-network-check-target-ip-10-0-128-48 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-48.ec2.internal uid: 67d8d4c1-6d5d-4629-b927-577243a38576 resourceVersion: "56477" uid: 682525c6-eedb-4fd1-a126-3ae53afc2d2a spec: sourcePod: network-check-source-7bc5b6bf85-srh28 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-18T01:58:42Z" message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.340597ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:26:42Z" - latency: 1.204825ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:25:42Z" - latency: 1.127226ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:24:42Z" - latency: 1.112881ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:23:42Z" - latency: 947.03µs message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:22:42Z" - latency: 1.206425ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:21:42Z" - latency: 1.3092ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:20:42Z" - latency: 1.059423ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:19:42Z" - latency: 1.285407ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:18:42Z" - latency: 1.119665ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:17:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T01:51:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-48-to-network-check-target-ip-10-0-135-157 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-48.ec2.internal uid: 67d8d4c1-6d5d-4629-b927-577243a38576 resourceVersion: "56478" uid: f5f482e7-ce51-4f74-a727-401a9a3c278e spec: sourcePod: network-check-source-7bc5b6bf85-srh28 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-18T01:58:42Z" message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.363563ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:26:42Z" - latency: 2.499112ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:25:42Z" - latency: 2.128105ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:24:42Z" - latency: 2.149718ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:23:42Z" - latency: 2.16003ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:22:42Z" - latency: 2.556025ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:21:42Z" - latency: 2.035114ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:20:42Z" - latency: 2.127917ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:19:42Z" - latency: 2.248673ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:18:42Z" - latency: 2.625017ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:17:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T01:51:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-48-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-48.ec2.internal uid: 67d8d4c1-6d5d-4629-b927-577243a38576 resourceVersion: "57624" uid: e0ae64c7-e9fc-47dc-91f1-3f344c9b5f72 spec: sourcePod: network-check-source-7bc5b6bf85-srh28 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-18T01:57:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.163957ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:27:42Z" - latency: 1.939864ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T02:27:42Z" - latency: 1.346353ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:26:42Z" - latency: 1.878169ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T02:26:42Z" - latency: 778.564µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:25:42Z" - latency: 1.942138ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T02:25:42Z" - latency: 1.30954ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:24:42Z" - latency: 1.90603ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T02:24:42Z" - latency: 1.195709ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:23:42Z" - latency: 1.855139ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T02:23:42Z" kind: List metadata: resourceVersion: ""