apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:13:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-186-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-186.ec2.internal
      uid: 072e7108-4a02-48bd-ac02-56ed58ae918b
    resourceVersion: "22043"
    uid: b6c11b50-561b-40f6-9d1b-a4db76120aad
  spec:
    sourcePod: network-check-source-989f8b8dc-6r977
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:20:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 888.632µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:34:09Z"
    - latency: 1.004899ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:33:09Z"
    - latency: 1.024512ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:32:09Z"
    - latency: 867.678µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:31:09Z"
    - latency: 1.285917ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:30:09Z"
    - latency: 1.134364ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:29:09Z"
    - latency: 1.317423ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:28:09Z"
    - latency: 1.098189ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:27:09Z"
    - latency: 802.302µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:26:09Z"
    - latency: 820.698µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:25:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:13:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-186-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-186.ec2.internal
      uid: 072e7108-4a02-48bd-ac02-56ed58ae918b
    resourceVersion: "20619"
    uid: 4d06df47-2432-4eb1-9fbe-ef54caf17ef1
  spec:
    sourcePod: network-check-source-989f8b8dc-6r977
    targetEndpoint: a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:19:09Z"
      message: 'load-balancer-api-external: tcp connection to a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.570233ms
      message: 'load-balancer-api-external: tcp connection to a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:31:09Z"
    - latency: 9.250902ms
      message: 'load-balancer-api-external: resolved host name a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:31:09Z"
    - latency: 6.262482ms
      message: 'load-balancer-api-external: tcp connection to a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:30:09Z"
    - latency: 8.89584ms
      message: 'load-balancer-api-external: resolved host name a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:30:09Z"
    - latency: 4.600915ms
      message: 'load-balancer-api-external: tcp connection to a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:29:09Z"
    - latency: 7.765019ms
      message: 'load-balancer-api-external: resolved host name a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:29:09Z"
    - latency: 4.440243ms
      message: 'load-balancer-api-external: tcp connection to a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:28:09Z"
    - latency: 8.280847ms
      message: 'load-balancer-api-external: resolved host name a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:28:09Z"
    - latency: 5.479641ms
      message: 'load-balancer-api-external: tcp connection to a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:27:09Z"
    - latency: 7.555026ms
      message: 'load-balancer-api-external: resolved host name a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:27:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:13:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-186-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-186.ec2.internal
      uid: 072e7108-4a02-48bd-ac02-56ed58ae918b
    resourceVersion: "20620"
    uid: 1cae894e-4a9c-4414-92c3-4f3639cc451d
  spec:
    sourcePod: network-check-source-989f8b8dc-6r977
    targetEndpoint: a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:19:09Z"
      message: 'load-balancer-api-internal: tcp connection to a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.586921ms
      message: 'load-balancer-api-internal: tcp connection to a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:31:09Z"
    - latency: 9.144588ms
      message: 'load-balancer-api-internal: resolved host name a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:31:09Z"
    - latency: 4.920577ms
      message: 'load-balancer-api-internal: tcp connection to a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:30:09Z"
    - latency: 8.875043ms
      message: 'load-balancer-api-internal: resolved host name a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:30:09Z"
    - latency: 4.602547ms
      message: 'load-balancer-api-internal: tcp connection to a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:29:09Z"
    - latency: 7.687734ms
      message: 'load-balancer-api-internal: resolved host name a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:29:09Z"
    - latency: 4.443702ms
      message: 'load-balancer-api-internal: tcp connection to a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:28:09Z"
    - latency: 8.260836ms
      message: 'load-balancer-api-internal: resolved host name a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:28:09Z"
    - latency: 6.352024ms
      message: 'load-balancer-api-internal: tcp connection to a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:27:09Z"
    - latency: 7.516969ms
      message: 'load-balancer-api-internal: resolved host name a9dcec41aaac144bf8e6cab0d89b0ad3-f035b1ad92e33321.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:27:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:13:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-186-to-network-check-target-ip-10-0-139-136
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-186.ec2.internal
      uid: 072e7108-4a02-48bd-ac02-56ed58ae918b
    resourceVersion: "22040"
    uid: a8e4a03f-f151-46eb-a5ad-a0361177ef7b
  spec:
    sourcePod: network-check-source-989f8b8dc-6r977
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:20:09Z"
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.232936ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:34:09Z"
    - latency: 2.251993ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:33:09Z"
    - latency: 2.324416ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:32:09Z"
    - latency: 2.674705ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:31:09Z"
    - latency: 2.330512ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:30:09Z"
    - latency: 2.212779ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:29:09Z"
    - latency: 2.306172ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:28:09Z"
    - latency: 2.073949ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:27:09Z"
    - latency: 2.164148ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:26:09Z"
    - latency: 2.045963ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:25:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:13:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-186-to-network-check-target-ip-10-0-140-100
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-186.ec2.internal
      uid: 072e7108-4a02-48bd-ac02-56ed58ae918b
    resourceVersion: "22041"
    uid: 8450973f-acba-4e0b-a3a0-737c521ff866
  spec:
    sourcePod: network-check-source-989f8b8dc-6r977
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:20:09Z"
      message: 'network-check-target-ip-10-0-140-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.824246ms
      message: 'network-check-target-ip-10-0-140-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:34:09Z"
    - latency: 1.816674ms
      message: 'network-check-target-ip-10-0-140-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:33:09Z"
    - latency: 1.772427ms
      message: 'network-check-target-ip-10-0-140-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:32:09Z"
    - latency: 1.924044ms
      message: 'network-check-target-ip-10-0-140-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:31:09Z"
    - latency: 1.858539ms
      message: 'network-check-target-ip-10-0-140-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:30:09Z"
    - latency: 1.823524ms
      message: 'network-check-target-ip-10-0-140-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:29:09Z"
    - latency: 1.703094ms
      message: 'network-check-target-ip-10-0-140-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:28:09Z"
    - latency: 1.859592ms
      message: 'network-check-target-ip-10-0-140-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:27:09Z"
    - latency: 1.473905ms
      message: 'network-check-target-ip-10-0-140-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:26:09Z"
    - latency: 1.727401ms
      message: 'network-check-target-ip-10-0-140-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:25:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:13:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-186-to-network-check-target-ip-10-0-142-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-186.ec2.internal
      uid: 072e7108-4a02-48bd-ac02-56ed58ae918b
    resourceVersion: "22042"
    uid: 55220987-decb-4301-abd3-40429fad1deb
  spec:
    sourcePod: network-check-source-989f8b8dc-6r977
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:20:09Z"
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 895.858µs
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:34:09Z"
    - latency: 1.265575ms
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:33:09Z"
    - latency: 754.797µs
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:32:09Z"
    - latency: 1.577278ms
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:31:09Z"
    - latency: 1.497836ms
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:30:09Z"
    - latency: 813.778µs
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:29:09Z"
    - latency: 1.70188ms
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:28:09Z"
    - latency: 776.651µs
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:27:09Z"
    - latency: 1.394866ms
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:26:09Z"
    - latency: 978.038µs
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:25:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:13:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-186-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-186.ec2.internal
      uid: 072e7108-4a02-48bd-ac02-56ed58ae918b
    resourceVersion: "20618"
    uid: 9c4a99d0-bfd1-40e1-b33a-549c56b7fb18
  spec:
    sourcePod: network-check-source-989f8b8dc-6r977
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:19:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.222907ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:31:09Z"
    - latency: 1.708687ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:31:09Z"
    - latency: 1.136734ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:30:09Z"
    - latency: 1.7112ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:30:09Z"
    - latency: 1.115217ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:29:09Z"
    - latency: 1.548594ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:29:09Z"
    - latency: 1.277175ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:28:09Z"
    - latency: 1.644177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:28:09Z"
    - latency: 807.312µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:27:09Z"
    - latency: 1.822511ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:27:09Z"
kind: List
metadata:
  resourceVersion: ""