apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T23:07:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-79-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-79.ec2.internal
      uid: 472cf530-7cf9-42a2-b5bd-857f6fb91fcf
    resourceVersion: "56244"
    uid: cc010e6a-dead-4a01-8121-55683b306ecf
  spec:
    sourcePod: network-check-source-989f8b8dc-wtb28
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T23:14:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 766.557µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:42:02Z"
    - latency: 1.255773ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:41:02Z"
    - latency: 1.211781ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:40:02Z"
    - latency: 1.191355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:39:02Z"
    - latency: 818.378µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:38:02Z"
    - latency: 1.063194ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:37:02Z"
    - latency: 906.855µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:36:02Z"
    - latency: 896.664µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:35:02Z"
    - latency: 779.784µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:34:02Z"
    - latency: 1.549631ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:33:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T23:07:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-79-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-79.ec2.internal
      uid: 472cf530-7cf9-42a2-b5bd-857f6fb91fcf
    resourceVersion: "57135"
    uid: 8f9692f4-50df-4dfe-981a-c75491606517
  spec:
    sourcePod: network-check-source-989f8b8dc-wtb28
    targetEndpoint: a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T23:13:02Z"
      message: 'load-balancer-api-external: tcp connection to a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.67396ms
      message: 'load-balancer-api-external: tcp connection to a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:43:02Z"
    - latency: 10.02022ms
      message: 'load-balancer-api-external: resolved host name a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:43:02Z"
    - latency: 5.769836ms
      message: 'load-balancer-api-external: tcp connection to a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:42:02Z"
    - latency: 12.11954ms
      message: 'load-balancer-api-external: resolved host name a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:42:02Z"
    - latency: 6.219117ms
      message: 'load-balancer-api-external: tcp connection to a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:41:02Z"
    - latency: 11.860265ms
      message: 'load-balancer-api-external: resolved host name a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:41:02Z"
    - latency: 3.542237ms
      message: 'load-balancer-api-external: tcp connection to a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:40:02Z"
    - latency: 14.455522ms
      message: 'load-balancer-api-external: resolved host name a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:40:02Z"
    - latency: 8.021756ms
      message: 'load-balancer-api-external: tcp connection to a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:39:02Z"
    - latency: 12.360965ms
      message: 'load-balancer-api-external: resolved host name a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:39:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T23:07:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-79-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-79.ec2.internal
      uid: 472cf530-7cf9-42a2-b5bd-857f6fb91fcf
    resourceVersion: "57134"
    uid: 993aed73-e95e-4672-8670-568ba7f54e35
  spec:
    sourcePod: network-check-source-989f8b8dc-wtb28
    targetEndpoint: a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T23:13:02Z"
      message: 'load-balancer-api-internal: tcp connection to a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.756625ms
      message: 'load-balancer-api-internal: tcp connection to a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:43:02Z"
    - latency: 9.9871ms
      message: 'load-balancer-api-internal: resolved host name a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:43:02Z"
    - latency: 5.275085ms
      message: 'load-balancer-api-internal: tcp connection to a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:42:02Z"
    - latency: 12.145207ms
      message: 'load-balancer-api-internal: resolved host name a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:42:02Z"
    - latency: 6.168695ms
      message: 'load-balancer-api-internal: tcp connection to a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:41:02Z"
    - latency: 11.93314ms
      message: 'load-balancer-api-internal: resolved host name a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:41:02Z"
    - latency: 3.473795ms
      message: 'load-balancer-api-internal: tcp connection to a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:40:02Z"
    - latency: 14.473424ms
      message: 'load-balancer-api-internal: resolved host name a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:40:02Z"
    - latency: 4.540266ms
      message: 'load-balancer-api-internal: tcp connection to a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:39:02Z"
    - latency: 12.32605ms
      message: 'load-balancer-api-internal: resolved host name a66b1a9a2a6934ae194edfc19de0e7be-e23cb87818262e00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:39:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T23:07:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-79-to-network-check-target-ip-10-0-131-54
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-79.ec2.internal
      uid: 472cf530-7cf9-42a2-b5bd-857f6fb91fcf
    resourceVersion: "56242"
    uid: bb6d8bfc-0a9d-4824-89ed-39d6455b1a34
  spec:
    sourcePod: network-check-source-989f8b8dc-wtb28
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T23:14:02Z"
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.756977ms
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:42:02Z"
    - latency: 1.737546ms
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:41:02Z"
    - latency: 1.495741ms
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:40:02Z"
    - latency: 1.502936ms
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:39:02Z"
    - latency: 1.895109ms
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:38:02Z"
    - latency: 2.073119ms
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:37:02Z"
    - latency: 1.793054ms
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:36:02Z"
    - latency: 2.041385ms
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:35:02Z"
    - latency: 1.906395ms
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:34:02Z"
    - latency: 1.919808ms
      message: 'network-check-target-ip-10-0-131-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:33:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T23:07:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-79-to-network-check-target-ip-10-0-135-106
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-79.ec2.internal
      uid: 472cf530-7cf9-42a2-b5bd-857f6fb91fcf
    resourceVersion: "56243"
    uid: 8dcfff00-3cb5-434d-9e51-b3ec460007bc
  spec:
    sourcePod: network-check-source-989f8b8dc-wtb28
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T23:14:02Z"
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.212829ms
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:42:02Z"
    - latency: 2.093334ms
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:41:02Z"
    - latency: 2.371443ms
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:40:02Z"
    - latency: 1.979501ms
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:39:02Z"
    - latency: 2.109524ms
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:38:02Z"
    - latency: 2.212534ms
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:37:02Z"
    - latency: 2.331212ms
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:36:02Z"
    - latency: 1.973049ms
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:35:02Z"
    - latency: 2.116331ms
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:34:02Z"
    - latency: 2.365888ms
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:33:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T23:07:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-79-to-network-check-target-ip-10-0-140-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-79.ec2.internal
      uid: 472cf530-7cf9-42a2-b5bd-857f6fb91fcf
    resourceVersion: "56241"
    uid: 4a81394d-3e0c-490f-b2c7-93c8ca12ad2e
  spec:
    sourcePod: network-check-source-989f8b8dc-wtb28
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T23:14:02Z"
      message: 'network-check-target-ip-10-0-140-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.353041ms
      message: 'network-check-target-ip-10-0-140-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:42:02Z"
    - latency: 904.386µs
      message: 'network-check-target-ip-10-0-140-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:41:02Z"
    - latency: 1.478108ms
      message: 'network-check-target-ip-10-0-140-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:40:02Z"
    - latency: 937.69µs
      message: 'network-check-target-ip-10-0-140-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:39:02Z"
    - latency: 1.267201ms
      message: 'network-check-target-ip-10-0-140-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:38:02Z"
    - latency: 780.282µs
      message: 'network-check-target-ip-10-0-140-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:37:02Z"
    - latency: 1.075835ms
      message: 'network-check-target-ip-10-0-140-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:36:02Z"
    - latency: 913.765µs
      message: 'network-check-target-ip-10-0-140-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:35:02Z"
    - latency: 1.490386ms
      message: 'network-check-target-ip-10-0-140-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:34:02Z"
    - latency: 1.598182ms
      message: 'network-check-target-ip-10-0-140-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:33:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T23:07:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-79-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-79.ec2.internal
      uid: 472cf530-7cf9-42a2-b5bd-857f6fb91fcf
    resourceVersion: "57131"
    uid: c59ff248-22de-424d-8ec4-c15b5fa94dfc
  spec:
    sourcePod: network-check-source-989f8b8dc-wtb28
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T23:13:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.029159ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:43:02Z"
    - latency: 1.895761ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:43:02Z"
    - latency: 874.245µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:42:02Z"
    - latency: 2.108154ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:42:02Z"
    - latency: 1.054966ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:41:02Z"
    - latency: 1.751774ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:41:02Z"
    - latency: 777.835µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:40:02Z"
    - latency: 1.992895ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:40:02Z"
    - latency: 805.078µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:39:02Z"
    - latency: 2.23706ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:39:02Z"
kind: List
metadata:
  resourceVersion: ""