apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:50:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-157-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-157.ec2.internal
      uid: f1cd8be9-da25-478b-96b5-7ed7f8fa080b
    resourceVersion: "22938"
    uid: e5269e9f-7093-4703-801a-e36860808c10
  spec:
    sourcePod: network-check-source-6f8b768455-tfj8x
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:57:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 794.295µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:11:08Z"
    - latency: 1.124561ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:10:08Z"
    - latency: 892.033µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:09:08Z"
    - latency: 1.083218ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:08Z"
    - latency: 1.056196ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:08Z"
    - latency: 838.412µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:08Z"
    - latency: 1.017438ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:08Z"
    - latency: 1.223818ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:08Z"
    - latency: 773.224µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:08Z"
    - latency: 926.946µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:50:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-157-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-157.ec2.internal
      uid: f1cd8be9-da25-478b-96b5-7ed7f8fa080b
    resourceVersion: "24351"
    uid: c816b874-1ea2-45eb-94aa-1a35c81d540b
  spec:
    sourcePod: network-check-source-6f8b768455-tfj8x
    targetEndpoint: a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:56:08Z"
      message: 'load-balancer-api-external: tcp connection to a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.204262ms
      message: 'load-balancer-api-external: tcp connection to a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:14:08Z"
    - latency: 6.097339ms
      message: 'load-balancer-api-external: resolved host name a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:14:08Z"
    - latency: 6.244084ms
      message: 'load-balancer-api-external: tcp connection to a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:13:08Z"
    - latency: 6.647307ms
      message: 'load-balancer-api-external: resolved host name a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:13:08Z"
    - latency: 5.497606ms
      message: 'load-balancer-api-external: tcp connection to a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:12:08Z"
    - latency: 6.999295ms
      message: 'load-balancer-api-external: resolved host name a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:12:08Z"
    - latency: 4.604494ms
      message: 'load-balancer-api-external: tcp connection to a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:11:08Z"
    - latency: 6.415059ms
      message: 'load-balancer-api-external: resolved host name a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:11:08Z"
    - latency: 4.871028ms
      message: 'load-balancer-api-external: tcp connection to a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:10:08Z"
    - latency: 5.980813ms
      message: 'load-balancer-api-external: resolved host name a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:10:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:50:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-157-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-157.ec2.internal
      uid: f1cd8be9-da25-478b-96b5-7ed7f8fa080b
    resourceVersion: "24350"
    uid: 6361d589-d97d-42ba-9d04-af5dd3b0c745
  spec:
    sourcePod: network-check-source-6f8b768455-tfj8x
    targetEndpoint: a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:56:08Z"
      message: 'load-balancer-api-internal: tcp connection to a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.689896ms
      message: 'load-balancer-api-internal: tcp connection to a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:14:08Z"
    - latency: 6.065626ms
      message: 'load-balancer-api-internal: resolved host name a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:14:08Z"
    - latency: 4.571333ms
      message: 'load-balancer-api-internal: tcp connection to a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:13:08Z"
    - latency: 6.695538ms
      message: 'load-balancer-api-internal: resolved host name a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:13:08Z"
    - latency: 4.199953ms
      message: 'load-balancer-api-internal: tcp connection to a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:12:08Z"
    - latency: 6.968447ms
      message: 'load-balancer-api-internal: resolved host name a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:12:08Z"
    - latency: 4.615478ms
      message: 'load-balancer-api-internal: tcp connection to a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:11:08Z"
    - latency: 6.48894ms
      message: 'load-balancer-api-internal: resolved host name a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:11:08Z"
    - latency: 4.848974ms
      message: 'load-balancer-api-internal: tcp connection to a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:10:08Z"
    - latency: 5.963453ms
      message: 'load-balancer-api-internal: resolved host name a7a74e0f035e0488ab01b21626b9ba98-19ce8a8935b151b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:10:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:50:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-157-to-network-check-target-ip-10-0-128-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-157.ec2.internal
      uid: f1cd8be9-da25-478b-96b5-7ed7f8fa080b
    resourceVersion: "22935"
    uid: c0e2cdfc-e211-4aa9-8330-605a39d8e33f
  spec:
    sourcePod: network-check-source-6f8b768455-tfj8x
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:57:08Z"
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.148446ms
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:11:08Z"
    - latency: 1.216204ms
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:10:08Z"
    - latency: 1.35252ms
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:09:08Z"
    - latency: 1.172935ms
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:08Z"
    - latency: 856.889µs
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:08Z"
    - latency: 1.216937ms
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:08Z"
    - latency: 860.901µs
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:08Z"
    - latency: 788.132µs
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:08Z"
    - latency: 725.343µs
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:08Z"
    - latency: 935.357µs
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:50:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-157-to-network-check-target-ip-10-0-138-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-157.ec2.internal
      uid: f1cd8be9-da25-478b-96b5-7ed7f8fa080b
    resourceVersion: "22937"
    uid: fbd63904-0255-4493-a4b5-1714f8e73265
  spec:
    sourcePod: network-check-source-6f8b768455-tfj8x
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:57:08Z"
      message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.00096ms
      message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:11:08Z"
    - latency: 1.851358ms
      message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:10:08Z"
    - latency: 1.977016ms
      message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:09:08Z"
    - latency: 1.846592ms
      message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:08Z"
    - latency: 1.947101ms
      message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:08Z"
    - latency: 1.923159ms
      message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:08Z"
    - latency: 1.907134ms
      message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:08Z"
    - latency: 1.943392ms
      message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:08Z"
    - latency: 1.895803ms
      message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:08Z"
    - latency: 1.844081ms
      message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:50:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-157-to-network-check-target-ip-10-0-142-81
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-157.ec2.internal
      uid: f1cd8be9-da25-478b-96b5-7ed7f8fa080b
    resourceVersion: "22936"
    uid: 5d5e0693-710a-4ee2-9fd2-26d8f20ae84b
  spec:
    sourcePod: network-check-source-6f8b768455-tfj8x
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:57:08Z"
      message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.174848ms
      message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:11:08Z"
    - latency: 2.027465ms
      message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:10:08Z"
    - latency: 2.211857ms
      message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:09:08Z"
    - latency: 1.958449ms
      message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:08Z"
    - latency: 1.992171ms
      message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:08Z"
    - latency: 2.437594ms
      message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:08Z"
    - latency: 2.200043ms
      message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:08Z"
    - latency: 2.014647ms
      message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:08Z"
    - latency: 1.893588ms
      message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:08Z"
    - latency: 2.0753ms
      message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:50:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-157-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-157.ec2.internal
      uid: f1cd8be9-da25-478b-96b5-7ed7f8fa080b
    resourceVersion: "24349"
    uid: e32e84c7-806b-4607-afe9-90ff0e18d006
  spec:
    sourcePod: network-check-source-6f8b768455-tfj8x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:56:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.23245ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:14:08Z"
    - latency: 1.58782ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:14:08Z"
    - latency: 1.100043ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:13:08Z"
    - latency: 1.47303ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:13:08Z"
    - latency: 941.328µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:12:08Z"
    - latency: 1.758547ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:12:08Z"
    - latency: 960.92µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:11:08Z"
    - latency: 1.950433ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:11:08Z"
    - latency: 832.089µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:10:08Z"
    - latency: 1.826436ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:10:08Z"
kind: List
metadata:
  resourceVersion: ""