apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T00:36:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-137-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-137.ec2.internal
      uid: f61e638b-8bdd-47a3-b37a-360a385affd1
    resourceVersion: "46940"
    uid: a24bddd6-32fc-4603-b737-512e32a53843
  spec:
    sourcePod: network-check-source-685456655f-fgxt2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T00:43:15Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.68809ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:57:15Z"
    - latency: 1.171284ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:56:15Z"
    - latency: 992.292µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:55:15Z"
    - latency: 705.248µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:54:15Z"
    - latency: 923.863µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:53:15Z"
    - latency: 844.216µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:52:15Z"
    - latency: 856.108µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:51:15Z"
    - latency: 1.059927ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:50:15Z"
    - latency: 994.198µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:49:15Z"
    - latency: 1.040276ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:48:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T00:36:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-137-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-137.ec2.internal
      uid: f61e638b-8bdd-47a3-b37a-360a385affd1
    resourceVersion: "49491"
    uid: 3f39ac75-39fc-4417-b505-344dcd0e96d1
  spec:
    sourcePod: network-check-source-685456655f-fgxt2
    targetEndpoint: ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T00:42:15Z"
      message: 'load-balancer-api-external: tcp connection to ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.911594ms
      message: 'load-balancer-api-external: tcp connection to ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T01:00:15Z"
    - latency: 8.083542ms
      message: 'load-balancer-api-external: resolved host name ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T01:00:15Z"
    - latency: 5.672667ms
      message: 'load-balancer-api-external: tcp connection to ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:59:15Z"
    - latency: 7.92002ms
      message: 'load-balancer-api-external: resolved host name ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T00:59:15Z"
    - latency: 5.115941ms
      message: 'load-balancer-api-external: tcp connection to ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:58:15Z"
    - latency: 8.381938ms
      message: 'load-balancer-api-external: resolved host name ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T00:58:15Z"
    - latency: 3.524777ms
      message: 'load-balancer-api-external: tcp connection to ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:57:15Z"
    - latency: 7.845183ms
      message: 'load-balancer-api-external: resolved host name ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T00:57:15Z"
    - latency: 4.06136ms
      message: 'load-balancer-api-external: tcp connection to ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:56:15Z"
    - latency: 7.733587ms
      message: 'load-balancer-api-external: resolved host name ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T00:56:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T00:36:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-137-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-137.ec2.internal
      uid: f61e638b-8bdd-47a3-b37a-360a385affd1
    resourceVersion: "49490"
    uid: edd43afa-8798-40ce-9fe0-795c81efb00b
  spec:
    sourcePod: network-check-source-685456655f-fgxt2
    targetEndpoint: ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T00:42:15Z"
      message: 'load-balancer-api-internal: tcp connection to ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.706641ms
      message: 'load-balancer-api-internal: tcp connection to ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T01:00:15Z"
    - latency: 8.138871ms
      message: 'load-balancer-api-internal: resolved host name ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T01:00:15Z"
    - latency: 4.44245ms
      message: 'load-balancer-api-internal: tcp connection to ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:59:15Z"
    - latency: 7.863874ms
      message: 'load-balancer-api-internal: resolved host name ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T00:59:15Z"
    - latency: 3.467686ms
      message: 'load-balancer-api-internal: tcp connection to ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:58:15Z"
    - latency: 8.325024ms
      message: 'load-balancer-api-internal: resolved host name ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T00:58:15Z"
    - latency: 5.341158ms
      message: 'load-balancer-api-internal: tcp connection to ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:57:15Z"
    - latency: 8.177066ms
      message: 'load-balancer-api-internal: resolved host name ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T00:57:15Z"
    - latency: 4.981974ms
      message: 'load-balancer-api-internal: tcp connection to ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:56:15Z"
    - latency: 7.801419ms
      message: 'load-balancer-api-internal: resolved host name ab6ee7c4fb9eb4f2295d3a6318dfc2da-ea57604c17c300dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T00:56:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T00:36:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-137-to-network-check-target-ip-10-0-139-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-137.ec2.internal
      uid: f61e638b-8bdd-47a3-b37a-360a385affd1
    resourceVersion: "46937"
    uid: ab307a97-8a26-40a7-94d4-e9f46c745dc6
  spec:
    sourcePod: network-check-source-685456655f-fgxt2
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T00:43:15Z"
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 958.285µs
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:57:15Z"
    - latency: 885.485µs
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:56:15Z"
    - latency: 731.272µs
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:55:15Z"
    - latency: 932.665µs
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:54:15Z"
    - latency: 867.436µs
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:53:15Z"
    - latency: 837.46µs
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:52:15Z"
    - latency: 797.075µs
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:51:15Z"
    - latency: 1.231577ms
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:50:15Z"
    - latency: 829.76µs
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:49:15Z"
    - latency: 918.387µs
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:48:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T00:36:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-137-to-network-check-target-ip-10-0-140-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-137.ec2.internal
      uid: f61e638b-8bdd-47a3-b37a-360a385affd1
    resourceVersion: "46939"
    uid: cefc79de-3312-452e-9ae7-8f0b55f1e604
  spec:
    sourcePod: network-check-source-685456655f-fgxt2
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T00:43:15Z"
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.37566ms
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:57:15Z"
    - latency: 2.152915ms
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:56:15Z"
    - latency: 2.289066ms
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:55:15Z"
    - latency: 2.430432ms
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:54:15Z"
    - latency: 2.22476ms
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:53:15Z"
    - latency: 2.400388ms
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:52:15Z"
    - latency: 1.910341ms
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:51:15Z"
    - latency: 2.755358ms
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:50:15Z"
    - latency: 2.006693ms
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:49:15Z"
    - latency: 1.896606ms
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:48:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T00:36:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-137-to-network-check-target-ip-10-0-142-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-137.ec2.internal
      uid: f61e638b-8bdd-47a3-b37a-360a385affd1
    resourceVersion: "46938"
    uid: 2d701169-7a4e-4394-a889-411208a4100c
  spec:
    sourcePod: network-check-source-685456655f-fgxt2
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T00:43:15Z"
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.869432ms
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:57:15Z"
    - latency: 1.768023ms
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:56:15Z"
    - latency: 2.189759ms
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:55:15Z"
    - latency: 2.003178ms
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:54:15Z"
    - latency: 1.989812ms
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:53:15Z"
    - latency: 2.050009ms
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:52:15Z"
    - latency: 1.973226ms
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:51:15Z"
    - latency: 2.175571ms
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:50:15Z"
    - latency: 2.090653ms
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:49:15Z"
    - latency: 1.989177ms
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:48:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T00:36:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-137-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-137.ec2.internal
      uid: f61e638b-8bdd-47a3-b37a-360a385affd1
    resourceVersion: "49489"
    uid: a0a25315-4eb2-4a5f-8218-57964d76a0a5
  spec:
    sourcePod: network-check-source-685456655f-fgxt2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T00:42:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 919.947µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T01:00:15Z"
    - latency: 1.909606ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T01:00:15Z"
    - latency: 897.336µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:59:15Z"
    - latency: 1.990438ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T00:59:15Z"
    - latency: 865.483µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:58:15Z"
    - latency: 1.735521ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T00:58:15Z"
    - latency: 963.684µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:57:15Z"
    - latency: 1.692125ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T00:57:15Z"
    - latency: 832.871µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T00:56:15Z"
    - latency: 1.970356ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T00:56:15Z"
kind: List
metadata:
  resourceVersion: ""