apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T19:27:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-228-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-228.ec2.internal
      uid: a5779268-655c-49e9-9e5d-f352b2f0e427
    resourceVersion: "44094"
    uid: 7a8fb7bd-2cff-464e-9087-b2720137396c
  spec:
    sourcePod: network-check-source-7f44b6dd87-qhvwr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T19:34:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.125338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:55:13Z"
    - latency: 1.033065ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:54:13Z"
    - latency: 837.277µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:53:13Z"
    - latency: 950.066µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:52:13Z"
    - latency: 1.011315ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:51:13Z"
    - latency: 853.76µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:50:13Z"
    - latency: 805.249µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:49:13Z"
    - latency: 832.069µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:48:13Z"
    - latency: 886.382µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:47:13Z"
    - latency: 731.289µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:46:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T19:27:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-228-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-228.ec2.internal
      uid: a5779268-655c-49e9-9e5d-f352b2f0e427
    resourceVersion: "46289"
    uid: c8c8752c-520c-4fe6-88d7-6768ca8680f6
  spec:
    sourcePod: network-check-source-7f44b6dd87-qhvwr
    targetEndpoint: a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T19:33:13Z"
      message: 'load-balancer-api-external: tcp connection to a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.853393ms
      message: 'load-balancer-api-external: tcp connection to a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:57:13Z"
    - latency: 10.970605ms
      message: 'load-balancer-api-external: resolved host name a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T19:57:13Z"
    - latency: 4.889878ms
      message: 'load-balancer-api-external: tcp connection to a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:56:13Z"
    - latency: 8.198042ms
      message: 'load-balancer-api-external: resolved host name a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T19:56:13Z"
    - latency: 4.611082ms
      message: 'load-balancer-api-external: tcp connection to a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:55:13Z"
    - latency: 7.514301ms
      message: 'load-balancer-api-external: resolved host name a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T19:55:13Z"
    - latency: 4.459981ms
      message: 'load-balancer-api-external: tcp connection to a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:54:13Z"
    - latency: 10.630382ms
      message: 'load-balancer-api-external: resolved host name a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T19:54:13Z"
    - latency: 5.395903ms
      message: 'load-balancer-api-external: tcp connection to a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:53:13Z"
    - latency: 8.276204ms
      message: 'load-balancer-api-external: resolved host name a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T19:53:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T19:27:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-228-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-228.ec2.internal
      uid: a5779268-655c-49e9-9e5d-f352b2f0e427
    resourceVersion: "46288"
    uid: 5467c2b6-b071-4c0f-9f69-b18ffe1e7d09
  spec:
    sourcePod: network-check-source-7f44b6dd87-qhvwr
    targetEndpoint: a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T19:33:13Z"
      message: 'load-balancer-api-internal: tcp connection to a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.698462ms
      message: 'load-balancer-api-internal: tcp connection to a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:57:13Z"
    - latency: 11.158677ms
      message: 'load-balancer-api-internal: resolved host name a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T19:57:13Z"
    - latency: 4.868049ms
      message: 'load-balancer-api-internal: tcp connection to a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:56:13Z"
    - latency: 8.301305ms
      message: 'load-balancer-api-internal: resolved host name a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T19:56:13Z"
    - latency: 4.311838ms
      message: 'load-balancer-api-internal: tcp connection to a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:55:13Z"
    - latency: 7.464092ms
      message: 'load-balancer-api-internal: resolved host name a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T19:55:13Z"
    - latency: 4.418823ms
      message: 'load-balancer-api-internal: tcp connection to a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:54:13Z"
    - latency: 10.684463ms
      message: 'load-balancer-api-internal: resolved host name a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T19:54:13Z"
    - latency: 5.376436ms
      message: 'load-balancer-api-internal: tcp connection to a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:53:13Z"
    - latency: 8.232521ms
      message: 'load-balancer-api-internal: resolved host name a254c758be231403abad9dfff9c6229e-531dea1401a6ca8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T19:53:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T19:27:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-228-to-network-check-target-ip-10-0-133-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-228.ec2.internal
      uid: a5779268-655c-49e9-9e5d-f352b2f0e427
    resourceVersion: "44092"
    uid: 161020ba-f697-446f-ae03-492c8ed6ec21
  spec:
    sourcePod: network-check-source-7f44b6dd87-qhvwr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T19:34:13Z"
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.491346ms
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:55:13Z"
    - latency: 693.088µs
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:54:13Z"
    - latency: 902.583µs
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:53:13Z"
    - latency: 827.403µs
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:52:13Z"
    - latency: 1.253213ms
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:51:13Z"
    - latency: 1.056167ms
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:50:13Z"
    - latency: 1.23404ms
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:49:13Z"
    - latency: 729.673µs
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:48:13Z"
    - latency: 835.195µs
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:47:13Z"
    - latency: 1.497864ms
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:46:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T19:27:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-228-to-network-check-target-ip-10-0-137-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-228.ec2.internal
      uid: a5779268-655c-49e9-9e5d-f352b2f0e427
    resourceVersion: "44091"
    uid: d368812b-26e5-4517-98cd-11a2a8d70629
  spec:
    sourcePod: network-check-source-7f44b6dd87-qhvwr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T19:34:13Z"
      message: 'network-check-target-ip-10-0-137-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.306301ms
      message: 'network-check-target-ip-10-0-137-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:55:13Z"
    - latency: 2.194534ms
      message: 'network-check-target-ip-10-0-137-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:54:13Z"
    - latency: 2.118679ms
      message: 'network-check-target-ip-10-0-137-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:53:13Z"
    - latency: 2.066485ms
      message: 'network-check-target-ip-10-0-137-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:52:13Z"
    - latency: 2.435139ms
      message: 'network-check-target-ip-10-0-137-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:51:13Z"
    - latency: 2.334158ms
      message: 'network-check-target-ip-10-0-137-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:50:13Z"
    - latency: 2.389492ms
      message: 'network-check-target-ip-10-0-137-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:49:13Z"
    - latency: 2.462574ms
      message: 'network-check-target-ip-10-0-137-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:48:13Z"
    - latency: 2.353594ms
      message: 'network-check-target-ip-10-0-137-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:47:13Z"
    - latency: 2.37657ms
      message: 'network-check-target-ip-10-0-137-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:46:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T19:27:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-228-to-network-check-target-ip-10-0-143-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-228.ec2.internal
      uid: a5779268-655c-49e9-9e5d-f352b2f0e427
    resourceVersion: "44093"
    uid: 3d5a34e1-9220-41ca-94da-3aeeea040339
  spec:
    sourcePod: network-check-source-7f44b6dd87-qhvwr
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T19:34:13Z"
      message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.28928ms
      message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:55:13Z"
    - latency: 2.434678ms
      message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:54:13Z"
    - latency: 2.422554ms
      message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:53:13Z"
    - latency: 2.019022ms
      message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:52:13Z"
    - latency: 2.390189ms
      message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:51:13Z"
    - latency: 2.274977ms
      message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:50:13Z"
    - latency: 2.093621ms
      message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:49:13Z"
    - latency: 2.362108ms
      message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:48:13Z"
    - latency: 2.349428ms
      message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:47:13Z"
    - latency: 1.917003ms
      message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:46:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T19:27:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-228-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-228.ec2.internal
      uid: a5779268-655c-49e9-9e5d-f352b2f0e427
    resourceVersion: "46286"
    uid: 28b8e640-5477-47d3-89cd-8c0b0de9c593
  spec:
    sourcePod: network-check-source-7f44b6dd87-qhvwr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T19:33:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.007624ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:57:13Z"
    - latency: 3.226612ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T19:57:13Z"
    - latency: 1.16411ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:56:13Z"
    - latency: 1.994704ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T19:56:13Z"
    - latency: 806.078µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:55:13Z"
    - latency: 1.509195ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T19:55:13Z"
    - latency: 854.589µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:54:13Z"
    - latency: 1.823615ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T19:54:13Z"
    - latency: 974.637µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T19:53:13Z"
    - latency: 1.722657ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T19:53:13Z"
kind: List
metadata:
  resourceVersion: ""