apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T03:03:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-225-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-225.ec2.internal
      uid: 64f79abd-f24b-49ac-974a-c21ee7af991d
    resourceVersion: "50772"
    uid: 380e744b-9503-4c84-99ef-eb91166c29b5
  spec:
    sourcePod: network-check-source-869dcfcdcd-stvgf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T03:10:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.037669ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:38:04Z"
    - latency: 1.186004ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:37:04Z"
    - latency: 1.081884ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:36:04Z"
    - latency: 1.121677ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:35:04Z"
    - latency: 928.073µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:34:04Z"
    - latency: 959.993µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:33:04Z"
    - latency: 941.252µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:32:04Z"
    - latency: 1.15874ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:31:04Z"
    - latency: 1.077612ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:30:04Z"
    - latency: 995.624µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:29:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T03:03:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-225-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-225.ec2.internal
      uid: 64f79abd-f24b-49ac-974a-c21ee7af991d
    resourceVersion: "51774"
    uid: 6b9bd326-5ca6-44b8-823d-0fe83cf54a26
  spec:
    sourcePod: network-check-source-869dcfcdcd-stvgf
    targetEndpoint: a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T03:09:04Z"
      message: 'load-balancer-api-external: tcp connection to a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.16478ms
      message: 'load-balancer-api-external: tcp connection to a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:39:04Z"
    - latency: 6.54452ms
      message: 'load-balancer-api-external: resolved host name a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T03:39:04Z"
    - latency: 5.147737ms
      message: 'load-balancer-api-external: tcp connection to a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:38:04Z"
    - latency: 6.869136ms
      message: 'load-balancer-api-external: resolved host name a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T03:38:04Z"
    - latency: 5.351806ms
      message: 'load-balancer-api-external: tcp connection to a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:37:04Z"
    - latency: 6.60582ms
      message: 'load-balancer-api-external: resolved host name a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T03:37:04Z"
    - latency: 5.013662ms
      message: 'load-balancer-api-external: tcp connection to a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:36:04Z"
    - latency: 7.826753ms
      message: 'load-balancer-api-external: resolved host name a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T03:36:04Z"
    - latency: 5.404701ms
      message: 'load-balancer-api-external: tcp connection to a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:35:04Z"
    - latency: 6.571087ms
      message: 'load-balancer-api-external: resolved host name a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T03:35:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T03:03:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-225-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-225.ec2.internal
      uid: 64f79abd-f24b-49ac-974a-c21ee7af991d
    resourceVersion: "51773"
    uid: 4a271034-8e19-4b94-9ef0-0f8873a01b40
  spec:
    sourcePod: network-check-source-869dcfcdcd-stvgf
    targetEndpoint: a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T03:09:04Z"
      message: 'load-balancer-api-internal: tcp connection to a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.961989ms
      message: 'load-balancer-api-internal: tcp connection to a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:39:04Z"
    - latency: 6.6307ms
      message: 'load-balancer-api-internal: resolved host name a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T03:39:04Z"
    - latency: 5.109962ms
      message: 'load-balancer-api-internal: tcp connection to a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:38:04Z"
    - latency: 6.942936ms
      message: 'load-balancer-api-internal: resolved host name a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T03:38:04Z"
    - latency: 4.958498ms
      message: 'load-balancer-api-internal: tcp connection to a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:37:04Z"
    - latency: 6.735445ms
      message: 'load-balancer-api-internal: resolved host name a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T03:37:04Z"
    - latency: 4.114032ms
      message: 'load-balancer-api-internal: tcp connection to a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:36:04Z"
    - latency: 7.727755ms
      message: 'load-balancer-api-internal: resolved host name a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T03:36:04Z"
    - latency: 5.363599ms
      message: 'load-balancer-api-internal: tcp connection to a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:35:04Z"
    - latency: 6.715927ms
      message: 'load-balancer-api-internal: resolved host name a30b3db99d1be4f67b66bf7bc249e499-9d26879ec29bf71e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T03:35:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T03:03:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-225-to-network-check-target-ip-10-0-130-225
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-225.ec2.internal
      uid: 64f79abd-f24b-49ac-974a-c21ee7af991d
    resourceVersion: "50769"
    uid: bbe095af-59ef-40ed-8cdd-6463d7eebea8
  spec:
    sourcePod: network-check-source-869dcfcdcd-stvgf
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T03:10:04Z"
      message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 894.52µs
      message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:38:04Z"
    - latency: 972.743µs
      message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:37:04Z"
    - latency: 1.30742ms
      message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:36:04Z"
    - latency: 984.598µs
      message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:35:04Z"
    - latency: 896.006µs
      message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:34:04Z"
    - latency: 968.218µs
      message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:33:04Z"
    - latency: 937.176µs
      message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:32:04Z"
    - latency: 965.106µs
      message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:31:04Z"
    - latency: 942.849µs
      message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:30:04Z"
    - latency: 915.804µs
      message: 'network-check-target-ip-10-0-130-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:29:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T03:03:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-225-to-network-check-target-ip-10-0-134-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-225.ec2.internal
      uid: 64f79abd-f24b-49ac-974a-c21ee7af991d
    resourceVersion: "50771"
    uid: 780c709c-282c-4f67-b8d9-3fa8bbf53ced
  spec:
    sourcePod: network-check-source-869dcfcdcd-stvgf
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T03:10:04Z"
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.364545ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:38:04Z"
    - latency: 1.928191ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:37:04Z"
    - latency: 2.442349ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:36:04Z"
    - latency: 1.966442ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:35:04Z"
    - latency: 1.907777ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:34:04Z"
    - latency: 2.256272ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:33:04Z"
    - latency: 2.311972ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:32:04Z"
    - latency: 2.29327ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:31:04Z"
    - latency: 2.331564ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:30:04Z"
    - latency: 2.178705ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:29:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T03:03:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-225-to-network-check-target-ip-10-0-142-39
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-225.ec2.internal
      uid: 64f79abd-f24b-49ac-974a-c21ee7af991d
    resourceVersion: "50770"
    uid: f7b34c03-8ddc-43b8-be4d-a3f1478b74a8
  spec:
    sourcePod: network-check-source-869dcfcdcd-stvgf
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T03:10:04Z"
      message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.24744ms
      message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:38:04Z"
    - latency: 2.134767ms
      message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:37:04Z"
    - latency: 2.35565ms
      message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:36:04Z"
    - latency: 2.287803ms
      message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:35:04Z"
    - latency: 2.061755ms
      message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:34:04Z"
    - latency: 2.611167ms
      message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:33:04Z"
    - latency: 2.370876ms
      message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:32:04Z"
    - latency: 2.212615ms
      message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:31:04Z"
    - latency: 2.342082ms
      message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:30:04Z"
    - latency: 2.235907ms
      message: 'network-check-target-ip-10-0-142-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:29:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T03:03:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-225-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-225.ec2.internal
      uid: 64f79abd-f24b-49ac-974a-c21ee7af991d
    resourceVersion: "51772"
    uid: 6f170eaf-e91a-4158-ae6c-1e8157f2538a
  spec:
    sourcePod: network-check-source-869dcfcdcd-stvgf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T03:09:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 904.308µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:39:04Z"
    - latency: 1.719023ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T03:39:04Z"
    - latency: 1.137225ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:38:04Z"
    - latency: 1.943244ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T03:38:04Z"
    - latency: 1.049083ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:37:04Z"
    - latency: 1.675625ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T03:37:04Z"
    - latency: 938.776µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:36:04Z"
    - latency: 1.617485ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T03:36:04Z"
    - latency: 863.371µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T03:35:04Z"
    - latency: 1.747853ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T03:35:04Z"
kind: List
metadata:
  resourceVersion: ""