apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:14:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-43-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-43.ec2.internal
      uid: 71232362-c6b9-4e67-ab78-123a2d837aed
    resourceVersion: "38147"
    uid: f57a903e-ae15-4a38-89db-99c4e6217914
  spec:
    sourcePod: network-check-source-7b678d77c7-wjllt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:21:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 953.741µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:42:39Z"
    - latency: 858.253µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:41:39Z"
    - latency: 1.067598ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:40:39Z"
    - latency: 1.004775ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:39:39Z"
    - latency: 1.190951ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:38:39Z"
    - latency: 1.496081ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:37:39Z"
    - latency: 2.377969ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:36:39Z"
    - latency: 1.009527ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:35:39Z"
    - latency: 1.275943ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:34:39Z"
    - latency: 1.457705ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:33:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:14:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-43-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-43.ec2.internal
      uid: 71232362-c6b9-4e67-ab78-123a2d837aed
    resourceVersion: "34566"
    uid: df51b63d-adef-4ea6-bae7-c35596f44bc6
  spec:
    sourcePod: network-check-source-7b678d77c7-wjllt
    targetEndpoint: abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:20:39Z"
      message: 'load-balancer-api-external: tcp connection to abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.917462ms
      message: 'load-balancer-api-external: tcp connection to abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:38:39Z"
    - latency: 10.140033ms
      message: 'load-balancer-api-external: resolved host name abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:38:39Z"
    - latency: 4.737253ms
      message: 'load-balancer-api-external: tcp connection to abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:37:39Z"
    - latency: 8.12929ms
      message: 'load-balancer-api-external: resolved host name abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:37:39Z"
    - latency: 6.200515ms
      message: 'load-balancer-api-external: tcp connection to abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:36:39Z"
    - latency: 9.252683ms
      message: 'load-balancer-api-external: resolved host name abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:36:39Z"
    - latency: 6.941422ms
      message: 'load-balancer-api-external: tcp connection to abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:35:39Z"
    - latency: 7.313039ms
      message: 'load-balancer-api-external: resolved host name abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:35:39Z"
    - latency: 4.275971ms
      message: 'load-balancer-api-external: tcp connection to abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:34:39Z"
    - latency: 6.741789ms
      message: 'load-balancer-api-external: resolved host name abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:34:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:14:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-43-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-43.ec2.internal
      uid: 71232362-c6b9-4e67-ab78-123a2d837aed
    resourceVersion: "34565"
    uid: fe08e366-503e-462a-b45c-0a47e5cbcbcb
  spec:
    sourcePod: network-check-source-7b678d77c7-wjllt
    targetEndpoint: abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:20:39Z"
      message: 'load-balancer-api-internal: tcp connection to abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.906829ms
      message: 'load-balancer-api-internal: tcp connection to abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:38:39Z"
    - latency: 10.21742ms
      message: 'load-balancer-api-internal: resolved host name abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:38:39Z"
    - latency: 4.559699ms
      message: 'load-balancer-api-internal: tcp connection to abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:37:39Z"
    - latency: 8.060397ms
      message: 'load-balancer-api-internal: resolved host name abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:37:39Z"
    - latency: 5.664039ms
      message: 'load-balancer-api-internal: tcp connection to abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:36:39Z"
    - latency: 9.751808ms
      message: 'load-balancer-api-internal: resolved host name abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:36:39Z"
    - latency: 9.631858ms
      message: 'load-balancer-api-internal: tcp connection to abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:35:39Z"
    - latency: 7.323942ms
      message: 'load-balancer-api-internal: resolved host name abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:35:39Z"
    - latency: 5.449048ms
      message: 'load-balancer-api-internal: tcp connection to abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:34:39Z"
    - latency: 6.687988ms
      message: 'load-balancer-api-internal: resolved host name abc8cf5c02b724531b9d43820bb29b6b-f466d6794e204296.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:34:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:14:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-43-to-network-check-target-ip-10-0-141-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-43.ec2.internal
      uid: 71232362-c6b9-4e67-ab78-123a2d837aed
    resourceVersion: "38146"
    uid: c4990a1d-77ba-45f5-97fb-81def43f9ae4
  spec:
    sourcePod: network-check-source-7b678d77c7-wjllt
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:21:39Z"
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.304954ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:42:39Z"
    - latency: 2.135896ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:41:39Z"
    - latency: 2.258597ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:40:39Z"
    - latency: 2.395172ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:39:39Z"
    - latency: 2.637426ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:38:39Z"
    - latency: 2.9504ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:37:39Z"
    - latency: 3.111655ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:36:39Z"
    - latency: 2.28483ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:35:39Z"
    - latency: 2.281918ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:34:39Z"
    - latency: 2.124398ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:33:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:14:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-43-to-network-check-target-ip-10-0-142-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-43.ec2.internal
      uid: 71232362-c6b9-4e67-ab78-123a2d837aed
    resourceVersion: "38145"
    uid: 089e14a4-8899-4638-9e8e-ec5d72e6daae
  spec:
    sourcePod: network-check-source-7b678d77c7-wjllt
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:21:39Z"
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.694564ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:42:39Z"
    - latency: 2.375593ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:41:39Z"
    - latency: 2.346622ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:40:39Z"
    - latency: 2.381584ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:39:39Z"
    - latency: 2.4325ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:38:39Z"
    - latency: 2.915393ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:37:39Z"
    - latency: 3.117287ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:36:39Z"
    - latency: 2.455004ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:35:39Z"
    - latency: 2.521735ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:34:39Z"
    - latency: 2.394919ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:33:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:14:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-43-to-network-check-target-ip-10-0-142-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-43.ec2.internal
      uid: 71232362-c6b9-4e67-ab78-123a2d837aed
    resourceVersion: "38144"
    uid: aaae0762-0a9b-4d19-ad06-78906e4cf791
  spec:
    sourcePod: network-check-source-7b678d77c7-wjllt
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:21:39Z"
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 901.093µs
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:42:39Z"
    - latency: 1.004271ms
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:41:39Z"
    - latency: 1.231688ms
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:40:39Z"
    - latency: 1.236572ms
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:39:39Z"
    - latency: 774.524µs
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:38:39Z"
    - latency: 779.739µs
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:37:39Z"
    - latency: 1.017936ms
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:36:39Z"
    - latency: 975.503µs
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:35:39Z"
    - latency: 1.215605ms
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:34:39Z"
    - latency: 1.127702ms
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:33:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:14:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-43-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-43.ec2.internal
      uid: 71232362-c6b9-4e67-ab78-123a2d837aed
    resourceVersion: "34563"
    uid: 9be82005-bcde-498c-b1b6-0c312d45ed51
  spec:
    sourcePod: network-check-source-7b678d77c7-wjllt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:20:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.157995ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:38:39Z"
    - latency: 1.744608ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:38:39Z"
    - latency: 1.352509ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:37:39Z"
    - latency: 2.777226ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:37:39Z"
    - latency: 1.462899ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:36:39Z"
    - latency: 2.445767ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:36:39Z"
    - latency: 980.749µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:35:39Z"
    - latency: 1.682488ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:35:39Z"
    - latency: 1.016413ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:34:39Z"
    - latency: 1.749057ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:34:39Z"
kind: List
metadata:
  resourceVersion: ""