apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T12:49:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-13-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-13.ec2.internal
      uid: 50086527-e2e5-40c4-83fb-dc20474971a1
    resourceVersion: "36544"
    uid: fac94e22-066b-4801-b3ce-23e329f91607
  spec:
    sourcePod: network-check-source-685456655f-wccw5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T12:56:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.017098ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:17:38Z"
    - latency: 814.171µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:16:38Z"
    - latency: 1.029472ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:15:38Z"
    - latency: 848.833µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:14:38Z"
    - latency: 1.12497ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:13:38Z"
    - latency: 1.157006ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:12:38Z"
    - latency: 789.733µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:11:38Z"
    - latency: 894.49µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:10:38Z"
    - latency: 983.384µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:09:38Z"
    - latency: 802.629µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:08:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T12:49:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-13-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-13.ec2.internal
      uid: 50086527-e2e5-40c4-83fb-dc20474971a1
    resourceVersion: "38057"
    uid: 61911e33-6452-4e7b-9fcc-a267367ba920
  spec:
    sourcePod: network-check-source-685456655f-wccw5
    targetEndpoint: a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T12:55:38Z"
      message: 'load-balancer-api-external: tcp connection to a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.267469ms
      message: 'load-balancer-api-external: tcp connection to a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:19:38Z"
    - latency: 7.911527ms
      message: 'load-balancer-api-external: resolved host name a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T13:19:38Z"
    - latency: 4.830546ms
      message: 'load-balancer-api-external: tcp connection to a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:18:38Z"
    - latency: 6.978593ms
      message: 'load-balancer-api-external: resolved host name a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T13:18:38Z"
    - latency: 4.517751ms
      message: 'load-balancer-api-external: tcp connection to a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:17:38Z"
    - latency: 7.210069ms
      message: 'load-balancer-api-external: resolved host name a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T13:17:38Z"
    - latency: 4.702661ms
      message: 'load-balancer-api-external: tcp connection to a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:16:38Z"
    - latency: 6.829616ms
      message: 'load-balancer-api-external: resolved host name a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T13:16:38Z"
    - latency: 4.73076ms
      message: 'load-balancer-api-external: tcp connection to a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:15:38Z"
    - latency: 6.254308ms
      message: 'load-balancer-api-external: resolved host name a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T13:15:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T12:49:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-13-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-13.ec2.internal
      uid: 50086527-e2e5-40c4-83fb-dc20474971a1
    resourceVersion: "38056"
    uid: 20524f12-9824-4ec5-8458-577f6fce5399
  spec:
    sourcePod: network-check-source-685456655f-wccw5
    targetEndpoint: a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T12:55:38Z"
      message: 'load-balancer-api-internal: tcp connection to a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.04396ms
      message: 'load-balancer-api-internal: tcp connection to a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:19:38Z"
    - latency: 7.972495ms
      message: 'load-balancer-api-internal: resolved host name a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T13:19:38Z"
    - latency: 4.859575ms
      message: 'load-balancer-api-internal: tcp connection to a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:18:38Z"
    - latency: 7.054949ms
      message: 'load-balancer-api-internal: resolved host name a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T13:18:38Z"
    - latency: 5.489129ms
      message: 'load-balancer-api-internal: tcp connection to a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:17:38Z"
    - latency: 7.167096ms
      message: 'load-balancer-api-internal: resolved host name a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T13:17:38Z"
    - latency: 4.631826ms
      message: 'load-balancer-api-internal: tcp connection to a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:16:38Z"
    - latency: 6.870779ms
      message: 'load-balancer-api-internal: resolved host name a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T13:16:38Z"
    - latency: 4.561654ms
      message: 'load-balancer-api-internal: tcp connection to a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:15:38Z"
    - latency: 6.314598ms
      message: 'load-balancer-api-internal: resolved host name a0a39b28daa8240908e177fbd18a5def-69e6cddf1ea128f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T13:15:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T12:49:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-13-to-network-check-target-ip-10-0-139-247
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-13.ec2.internal
      uid: 50086527-e2e5-40c4-83fb-dc20474971a1
    resourceVersion: "36543"
    uid: 3e3c1929-4dbc-4e33-9675-a67347b0974f
  spec:
    sourcePod: network-check-source-685456655f-wccw5
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T12:56:38Z"
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.248572ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:17:38Z"
    - latency: 2.344051ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:16:38Z"
    - latency: 2.513589ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:15:38Z"
    - latency: 2.175583ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:14:38Z"
    - latency: 2.247579ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:13:38Z"
    - latency: 2.116066ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:12:38Z"
    - latency: 2.22454ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:11:38Z"
    - latency: 2.234157ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:10:38Z"
    - latency: 2.322783ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:09:38Z"
    - latency: 2.200638ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:08:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T12:49:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-13-to-network-check-target-ip-10-0-141-13
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-13.ec2.internal
      uid: 50086527-e2e5-40c4-83fb-dc20474971a1
    resourceVersion: "36541"
    uid: 403548d0-bf66-4805-b5d3-c070dc7fff33
  spec:
    sourcePod: network-check-source-685456655f-wccw5
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T12:56:38Z"
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 937.575µs
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:17:38Z"
    - latency: 930.776µs
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:16:38Z"
    - latency: 933.068µs
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:15:38Z"
    - latency: 1.181084ms
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:14:38Z"
    - latency: 967.374µs
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:13:38Z"
    - latency: 919.28µs
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:12:38Z"
    - latency: 927.603µs
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:11:38Z"
    - latency: 807.949µs
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:10:38Z"
    - latency: 852.881µs
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:09:38Z"
    - latency: 1.180725ms
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:08:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T12:49:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-13-to-network-check-target-ip-10-0-143-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-13.ec2.internal
      uid: 50086527-e2e5-40c4-83fb-dc20474971a1
    resourceVersion: "36542"
    uid: d6ef87e6-b407-4c78-b1db-0e6af2aec8e4
  spec:
    sourcePod: network-check-source-685456655f-wccw5
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T12:56:38Z"
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.937342ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:17:38Z"
    - latency: 2.026271ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:16:38Z"
    - latency: 1.943147ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:15:38Z"
    - latency: 1.910615ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:14:38Z"
    - latency: 1.80833ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:13:38Z"
    - latency: 1.929026ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:12:38Z"
    - latency: 1.813853ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:11:38Z"
    - latency: 1.931518ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:10:38Z"
    - latency: 1.896017ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:09:38Z"
    - latency: 1.501724ms
      message: 'network-check-target-ip-10-0-143-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:08:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T12:49:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-13-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-13.ec2.internal
      uid: 50086527-e2e5-40c4-83fb-dc20474971a1
    resourceVersion: "38055"
    uid: 02218d4d-ae25-42e2-aaea-533e19e33b61
  spec:
    sourcePod: network-check-source-685456655f-wccw5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T12:55:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.068962ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:19:38Z"
    - latency: 1.860904ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T13:19:38Z"
    - latency: 835.636µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:18:38Z"
    - latency: 1.798454ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T13:18:38Z"
    - latency: 956.616µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:17:38Z"
    - latency: 2.127896ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T13:17:38Z"
    - latency: 773.8µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:16:38Z"
    - latency: 1.699824ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T13:16:38Z"
    - latency: 1.327978ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T13:15:38Z"
    - latency: 1.72912ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T13:15:38Z"
kind: List
metadata:
  resourceVersion: ""