apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:49:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-46-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-46.us-west-2.compute.internal
      uid: f87198a0-0c32-4659-be62-5e41efa95dec
    resourceVersion: "121857"
    uid: 311eb307-d67b-413c-893f-216b901bd2a2
  spec:
    sourcePod: network-check-source-6f78d59f99-f6bkw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:56:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 906.176µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:59:40Z"
    - latency: 1.755529ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:58:40Z"
    - latency: 1.775454ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:57:40Z"
    - latency: 1.330599ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:56:40Z"
    - latency: 1.790733ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:55:40Z"
    - latency: 927.231µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:54:40Z"
    - latency: 1.872424ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:53:40Z"
    - latency: 1.554391ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:52:40Z"
    - latency: 2.634713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:51:40Z"
    - latency: 1.266788ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:50:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:49:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-46-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-46.us-west-2.compute.internal
      uid: f87198a0-0c32-4659-be62-5e41efa95dec
    resourceVersion: "125220"
    uid: cc9ece21-95ce-4087-b4ba-7d27295a6dba
  spec:
    sourcePod: network-check-source-6f78d59f99-f6bkw
    targetEndpoint: a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:55:40Z"
      message: 'load-balancer-api-external: tcp connection to a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.166563ms
      message: 'load-balancer-api-external: tcp connection to a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:01:40Z"
    - latency: 11.006386ms
      message: 'load-balancer-api-external: resolved host name a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:01:40Z"
    - latency: 107.676461ms
      message: 'load-balancer-api-external: tcp connection to a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:00:40Z"
    - latency: 7.490168ms
      message: 'load-balancer-api-external: resolved host name a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:00:40Z"
    - latency: 54.622888ms
      message: 'load-balancer-api-external: tcp connection to a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:59:40Z"
    - latency: 6.768892ms
      message: 'load-balancer-api-external: resolved host name a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:59:40Z"
    - latency: 53.089779ms
      message: 'load-balancer-api-external: tcp connection to a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:58:40Z"
    - latency: 8.408688ms
      message: 'load-balancer-api-external: resolved host name a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:58:40Z"
    - latency: 57.060509ms
      message: 'load-balancer-api-external: tcp connection to a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:57:40Z"
    - latency: 7.639438ms
      message: 'load-balancer-api-external: resolved host name a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:57:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:49:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-46-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-46.us-west-2.compute.internal
      uid: f87198a0-0c32-4659-be62-5e41efa95dec
    resourceVersion: "125219"
    uid: c04c1ab9-c830-426a-b994-28badb012ed6
  spec:
    sourcePod: network-check-source-6f78d59f99-f6bkw
    targetEndpoint: a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:55:40Z"
      message: 'load-balancer-api-internal: tcp connection to a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 52.126754ms
      message: 'load-balancer-api-internal: tcp connection to a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:01:40Z"
    - latency: 11.039118ms
      message: 'load-balancer-api-internal: resolved host name a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:01:40Z"
    - latency: 110.792245ms
      message: 'load-balancer-api-internal: tcp connection to a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:00:40Z"
    - latency: 7.52829ms
      message: 'load-balancer-api-internal: resolved host name a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:00:40Z"
    - latency: 59.575183ms
      message: 'load-balancer-api-internal: tcp connection to a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:59:40Z"
    - latency: 6.816511ms
      message: 'load-balancer-api-internal: resolved host name a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:59:40Z"
    - latency: 49.986667ms
      message: 'load-balancer-api-internal: tcp connection to a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:58:40Z"
    - latency: 8.445323ms
      message: 'load-balancer-api-internal: resolved host name a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:58:40Z"
    - latency: 58.354098ms
      message: 'load-balancer-api-internal: tcp connection to a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:57:40Z"
    - latency: 7.418744ms
      message: 'load-balancer-api-internal: resolved host name a08f964132a324d829023bb7d5fff707-ee203c489136d9c1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:57:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:49:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-46-to-network-check-target-ip-10-0-136-46
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-46.us-west-2.compute.internal
      uid: f87198a0-0c32-4659-be62-5e41efa95dec
    resourceVersion: "121848"
    uid: 39ea32be-5b69-47e5-b4eb-73e07ab75d6c
  spec:
    sourcePod: network-check-source-6f78d59f99-f6bkw
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:56:40Z"
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.257809ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:59:40Z"
    - latency: 978.427µs
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:58:40Z"
    - latency: 1.214187ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:57:40Z"
    - latency: 2.214935ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:56:40Z"
    - latency: 1.795255ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:55:40Z"
    - latency: 1.034832ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:54:40Z"
    - latency: 1.324989ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:53:40Z"
    - latency: 1.217602ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:52:40Z"
    - latency: 1.716789ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:51:40Z"
    - latency: 1.729474ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:50:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:49:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-46-to-network-check-target-ip-10-0-139-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-46.us-west-2.compute.internal
      uid: f87198a0-0c32-4659-be62-5e41efa95dec
    resourceVersion: "121849"
    uid: eb883b46-d54b-4efd-9509-cf28c942070e
  spec:
    sourcePod: network-check-source-6f78d59f99-f6bkw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:56:40Z"
      message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.98898ms
      message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:59:40Z"
    - latency: 2.416479ms
      message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:58:40Z"
    - latency: 2.363535ms
      message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:57:40Z"
    - latency: 3.326598ms
      message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:56:40Z"
    - latency: 2.319257ms
      message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:55:40Z"
    - latency: 2.486204ms
      message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:54:40Z"
    - latency: 2.482938ms
      message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:53:40Z"
    - latency: 2.951391ms
      message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:52:40Z"
    - latency: 3.0519ms
      message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:51:40Z"
    - latency: 2.228272ms
      message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:50:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:49:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-46-to-network-check-target-ip-10-0-143-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-46.us-west-2.compute.internal
      uid: f87198a0-0c32-4659-be62-5e41efa95dec
    resourceVersion: "121854"
    uid: 8657a265-2406-4b78-a236-781d11ee2c60
  spec:
    sourcePod: network-check-source-6f78d59f99-f6bkw
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:56:40Z"
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.153505ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:59:40Z"
    - latency: 2.587679ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:58:40Z"
    - latency: 3.261859ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:57:40Z"
    - latency: 2.404599ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:56:40Z"
    - latency: 2.62393ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:55:40Z"
    - latency: 2.199112ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:54:40Z"
    - latency: 2.769171ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:53:40Z"
    - latency: 2.712419ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:52:40Z"
    - latency: 3.463531ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:51:40Z"
    - latency: 2.18144ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:50:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:49:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-46-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-46.us-west-2.compute.internal
      uid: f87198a0-0c32-4659-be62-5e41efa95dec
    resourceVersion: "125216"
    uid: aa770f4a-a00c-4527-b721-83a769e457e3
  spec:
    sourcePod: network-check-source-6f78d59f99-f6bkw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:55:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.170682ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:01:40Z"
    - latency: 1.817659ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:01:40Z"
    - latency: 1.309038ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:00:40Z"
    - latency: 1.84362ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:00:40Z"
    - latency: 1.204995ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:59:40Z"
    - latency: 1.890599ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:59:40Z"
    - latency: 1.203475ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:58:40Z"
    - latency: 1.925164ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:58:40Z"
    - latency: 1.460258ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:57:40Z"
    - latency: 2.549563ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:57:40Z"
kind: List
metadata:
  resourceVersion: ""