apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T06:30:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-30-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-30.ec2.internal
      uid: bc295d8d-9231-48ec-bc4e-17dc516041f9
    resourceVersion: "70132"
    uid: 3747f717-85cb-4507-b08e-5e1c497153b1
  spec:
    sourcePod: network-check-source-7cbc45fddc-tgxrx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T06:37:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 996.174µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:05:07Z"
    - latency: 1.372637ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:04:07Z"
    - latency: 1.083228ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:03:07Z"
    - latency: 837.898µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:02:07Z"
    - latency: 969.993µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:01:07Z"
    - latency: 961.515µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:00:07Z"
    - latency: 1.129999ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T06:59:07Z"
    - latency: 812.337µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T06:58:07Z"
    - latency: 896.073µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T06:57:07Z"
    - latency: 921.035µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T06:56:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T06:30:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-30-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-30.ec2.internal
      uid: bc295d8d-9231-48ec-bc4e-17dc516041f9
    resourceVersion: "70960"
    uid: 65d0a24d-520e-403e-a658-d056bf6c8444
  spec:
    sourcePod: network-check-source-7cbc45fddc-tgxrx
    targetEndpoint: a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T06:36:07Z"
      message: 'load-balancer-api-external: tcp connection to a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.157686ms
      message: 'load-balancer-api-external: tcp connection to a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:06:07Z"
    - latency: 6.697673ms
      message: 'load-balancer-api-external: resolved host name a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T07:06:07Z"
    - latency: 3.093536ms
      message: 'load-balancer-api-external: tcp connection to a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:05:07Z"
    - latency: 6.483446ms
      message: 'load-balancer-api-external: resolved host name a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T07:05:07Z"
    - latency: 5.142752ms
      message: 'load-balancer-api-external: tcp connection to a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:04:07Z"
    - latency: 5.658375ms
      message: 'load-balancer-api-external: resolved host name a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T07:04:07Z"
    - latency: 4.566993ms
      message: 'load-balancer-api-external: tcp connection to a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:03:07Z"
    - latency: 6.998842ms
      message: 'load-balancer-api-external: resolved host name a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T07:03:07Z"
    - latency: 5.377727ms
      message: 'load-balancer-api-external: tcp connection to a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:02:07Z"
    - latency: 6.863367ms
      message: 'load-balancer-api-external: resolved host name a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T07:02:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T06:30:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-30-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-30.ec2.internal
      uid: bc295d8d-9231-48ec-bc4e-17dc516041f9
    resourceVersion: "70959"
    uid: ecf7b038-d119-4e40-a43a-a6e5a2073539
  spec:
    sourcePod: network-check-source-7cbc45fddc-tgxrx
    targetEndpoint: a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T06:36:07Z"
      message: 'load-balancer-api-internal: tcp connection to a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.585045ms
      message: 'load-balancer-api-internal: tcp connection to a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:06:07Z"
    - latency: 6.572864ms
      message: 'load-balancer-api-internal: resolved host name a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T07:06:07Z"
    - latency: 5.07271ms
      message: 'load-balancer-api-internal: tcp connection to a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:05:07Z"
    - latency: 6.571628ms
      message: 'load-balancer-api-internal: resolved host name a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T07:05:07Z"
    - latency: 4.673945ms
      message: 'load-balancer-api-internal: tcp connection to a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:04:07Z"
    - latency: 5.483268ms
      message: 'load-balancer-api-internal: resolved host name a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T07:04:07Z"
    - latency: 5.246655ms
      message: 'load-balancer-api-internal: tcp connection to a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:03:07Z"
    - latency: 6.841777ms
      message: 'load-balancer-api-internal: resolved host name a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T07:03:07Z"
    - latency: 5.714447ms
      message: 'load-balancer-api-internal: tcp connection to a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:02:07Z"
    - latency: 6.804945ms
      message: 'load-balancer-api-internal: resolved host name a8cd3a861f5b14648804a8d3fece3f1d-fda53f0cda5caaed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T07:02:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T06:30:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-30-to-network-check-target-ip-10-0-128-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-30.ec2.internal
      uid: bc295d8d-9231-48ec-bc4e-17dc516041f9
    resourceVersion: "70129"
    uid: 43baaf7a-8268-4274-b58c-d313939d0172
  spec:
    sourcePod: network-check-source-7cbc45fddc-tgxrx
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T06:37:07Z"
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.002072ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:05:07Z"
    - latency: 905.622µs
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:04:07Z"
    - latency: 932.738µs
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:03:07Z"
    - latency: 1.423832ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:02:07Z"
    - latency: 1.302121ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:01:07Z"
    - latency: 934.203µs
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:00:07Z"
    - latency: 1.297801ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T06:59:07Z"
    - latency: 861.176µs
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T06:58:07Z"
    - latency: 1.399772ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T06:57:07Z"
    - latency: 874.526µs
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T06:56:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T06:30:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-30-to-network-check-target-ip-10-0-142-104
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-30.ec2.internal
      uid: bc295d8d-9231-48ec-bc4e-17dc516041f9
    resourceVersion: "70131"
    uid: d3e79023-c8c0-4c11-baa8-27436f95b9ce
  spec:
    sourcePod: network-check-source-7cbc45fddc-tgxrx
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T06:37:07Z"
      message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.46662ms
      message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:05:07Z"
    - latency: 2.6171ms
      message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:04:07Z"
    - latency: 2.387814ms
      message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:03:07Z"
    - latency: 2.358803ms
      message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:02:07Z"
    - latency: 2.235428ms
      message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:01:07Z"
    - latency: 2.53814ms
      message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:00:07Z"
    - latency: 2.315563ms
      message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T06:59:07Z"
    - latency: 2.697731ms
      message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T06:58:07Z"
    - latency: 2.574953ms
      message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T06:57:07Z"
    - latency: 2.382476ms
      message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T06:56:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T06:30:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-30-to-network-check-target-ip-10-0-143-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-30.ec2.internal
      uid: bc295d8d-9231-48ec-bc4e-17dc516041f9
    resourceVersion: "70130"
    uid: 60f6aa3f-2ea8-4ef5-be51-51ba4d6e16dd
  spec:
    sourcePod: network-check-source-7cbc45fddc-tgxrx
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T06:37:07Z"
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.467085ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:05:07Z"
    - latency: 2.416524ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:04:07Z"
    - latency: 2.003523ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:03:07Z"
    - latency: 2.577287ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:02:07Z"
    - latency: 2.637921ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:01:07Z"
    - latency: 2.708623ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:00:07Z"
    - latency: 2.63541ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T06:59:07Z"
    - latency: 2.150736ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T06:58:07Z"
    - latency: 1.97449ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T06:57:07Z"
    - latency: 2.424438ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T06:56:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T06:30:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-30-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-30.ec2.internal
      uid: bc295d8d-9231-48ec-bc4e-17dc516041f9
    resourceVersion: "70958"
    uid: 1cd9f1d4-445d-4aa9-94ee-15f64ba9c1fb
  spec:
    sourcePod: network-check-source-7cbc45fddc-tgxrx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T06:36:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 993.118µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:06:07Z"
    - latency: 1.560926ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T07:06:07Z"
    - latency: 907.576µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:05:07Z"
    - latency: 1.769953ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T07:05:07Z"
    - latency: 857.169µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:04:07Z"
    - latency: 1.746043ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T07:04:07Z"
    - latency: 954.367µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:03:07Z"
    - latency: 1.754857ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T07:03:07Z"
    - latency: 989.853µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T07:02:07Z"
    - latency: 1.822768ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T07:02:07Z"
kind: List
metadata:
  resourceVersion: ""