apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T19:05:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-99-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-99.ec2.internal
      uid: a43fc4d6-35d4-468c-8782-1db8bdee4b6f
    resourceVersion: "70772"
    uid: aa398301-e86a-414b-b2fe-e0e20ca6f53f
  spec:
    sourcePod: network-check-source-7d88cb55d8-c8svl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T19:12:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.271967ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:54:48Z"
    - latency: 876.366µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:53:48Z"
    - latency: 893.422µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:52:48Z"
    - latency: 1.115119ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:51:48Z"
    - latency: 1.190344ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:50:48Z"
    - latency: 1.065447ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:49:48Z"
    - latency: 1.03537ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:48:48Z"
    - latency: 1.01352ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:47:48Z"
    - latency: 1.185432ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:46:48Z"
    - latency: 1.297144ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:45:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T19:05:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-99-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-99.ec2.internal
      uid: a43fc4d6-35d4-468c-8782-1db8bdee4b6f
    resourceVersion: "68741"
    uid: 08dad8f6-2b13-4238-8fdc-78e5a886d2c4
  spec:
    sourcePod: network-check-source-7d88cb55d8-c8svl
    targetEndpoint: a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T19:11:48Z"
      message: 'load-balancer-api-external: tcp connection to a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.925322ms
      message: 'load-balancer-api-external: tcp connection to a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:53:48Z"
    - latency: 8.743276ms
      message: 'load-balancer-api-external: resolved host name a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:53:48Z"
    - latency: 4.483127ms
      message: 'load-balancer-api-external: tcp connection to a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:52:48Z"
    - latency: 8.402869ms
      message: 'load-balancer-api-external: resolved host name a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:52:48Z"
    - latency: 4.274316ms
      message: 'load-balancer-api-external: tcp connection to a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:51:48Z"
    - latency: 6.560546ms
      message: 'load-balancer-api-external: resolved host name a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:51:48Z"
    - latency: 4.871872ms
      message: 'load-balancer-api-external: tcp connection to a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:50:48Z"
    - latency: 6.880112ms
      message: 'load-balancer-api-external: resolved host name a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:50:48Z"
    - latency: 3.317373ms
      message: 'load-balancer-api-external: tcp connection to a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:49:48Z"
    - latency: 9.198429ms
      message: 'load-balancer-api-external: resolved host name a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:49:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T19:05:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-99-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-99.ec2.internal
      uid: a43fc4d6-35d4-468c-8782-1db8bdee4b6f
    resourceVersion: "68742"
    uid: 569896bf-e017-4f6d-b6b5-5203e50c2988
  spec:
    sourcePod: network-check-source-7d88cb55d8-c8svl
    targetEndpoint: a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T19:11:48Z"
      message: 'load-balancer-api-internal: tcp connection to a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.928213ms
      message: 'load-balancer-api-internal: tcp connection to a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:53:48Z"
    - latency: 8.769485ms
      message: 'load-balancer-api-internal: resolved host name a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:53:48Z"
    - latency: 4.494785ms
      message: 'load-balancer-api-internal: tcp connection to a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:52:48Z"
    - latency: 8.329245ms
      message: 'load-balancer-api-internal: resolved host name a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:52:48Z"
    - latency: 4.601209ms
      message: 'load-balancer-api-internal: tcp connection to a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:51:48Z"
    - latency: 6.486987ms
      message: 'load-balancer-api-internal: resolved host name a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:51:48Z"
    - latency: 4.839781ms
      message: 'load-balancer-api-internal: tcp connection to a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:50:48Z"
    - latency: 6.900603ms
      message: 'load-balancer-api-internal: resolved host name a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:50:48Z"
    - latency: 4.107527ms
      message: 'load-balancer-api-internal: tcp connection to a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:49:48Z"
    - latency: 9.167925ms
      message: 'load-balancer-api-internal: resolved host name a3c8c5d52a97344b99ef1443d8dc3b02-c552c2e271edfd1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:49:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T19:05:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-99-to-network-check-target-ip-10-0-137-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-99.ec2.internal
      uid: a43fc4d6-35d4-468c-8782-1db8bdee4b6f
    resourceVersion: "70770"
    uid: 2df0c5c0-18bd-46d3-a1cd-a0e84f871dff
  spec:
    sourcePod: network-check-source-7d88cb55d8-c8svl
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T19:12:48Z"
      message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.045415ms
      message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:54:48Z"
    - latency: 1.793832ms
      message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:53:48Z"
    - latency: 1.780779ms
      message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:52:48Z"
    - latency: 2.141355ms
      message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:51:48Z"
    - latency: 2.008154ms
      message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:50:48Z"
    - latency: 1.401192ms
      message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:49:48Z"
    - latency: 1.641602ms
      message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:48:48Z"
    - latency: 1.636359ms
      message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:47:48Z"
    - latency: 1.6466ms
      message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:46:48Z"
    - latency: 1.925029ms
      message: 'network-check-target-ip-10-0-137-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:45:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T19:05:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-99-to-network-check-target-ip-10-0-138-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-99.ec2.internal
      uid: a43fc4d6-35d4-468c-8782-1db8bdee4b6f
    resourceVersion: "70771"
    uid: 997cb87e-8acf-4bae-969c-b50da73008d8
  spec:
    sourcePod: network-check-source-7d88cb55d8-c8svl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T19:12:48Z"
      message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.164116ms
      message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:54:48Z"
    - latency: 2.242022ms
      message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:53:48Z"
    - latency: 2.408496ms
      message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:52:48Z"
    - latency: 2.260058ms
      message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:51:48Z"
    - latency: 2.209756ms
      message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:50:48Z"
    - latency: 1.889499ms
      message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:49:48Z"
    - latency: 1.98558ms
      message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:48:48Z"
    - latency: 2.129509ms
      message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:47:48Z"
    - latency: 2.114379ms
      message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:46:48Z"
    - latency: 2.181704ms
      message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:45:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T19:05:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-99-to-network-check-target-ip-10-0-142-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-99.ec2.internal
      uid: a43fc4d6-35d4-468c-8782-1db8bdee4b6f
    resourceVersion: "70769"
    uid: a0938368-5efc-4b10-8a1f-b30cc7c31b5a
  spec:
    sourcePod: network-check-source-7d88cb55d8-c8svl
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T19:12:48Z"
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 832.505µs
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:54:48Z"
    - latency: 1.07146ms
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:53:48Z"
    - latency: 1.014633ms
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:52:48Z"
    - latency: 973.84µs
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:51:48Z"
    - latency: 902.66µs
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:50:48Z"
    - latency: 1.600694ms
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:49:48Z"
    - latency: 901.047µs
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:48:48Z"
    - latency: 1.26064ms
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:47:48Z"
    - latency: 888.671µs
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:46:48Z"
    - latency: 993.052µs
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:45:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T19:05:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-99-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-99.ec2.internal
      uid: a43fc4d6-35d4-468c-8782-1db8bdee4b6f
    resourceVersion: "68740"
    uid: fd416492-6ba0-4c0a-a39d-24d17750960b
  spec:
    sourcePod: network-check-source-7d88cb55d8-c8svl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T19:11:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 917.019µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:53:48Z"
    - latency: 1.701156ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:53:48Z"
    - latency: 891.292µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:52:48Z"
    - latency: 1.573514ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:52:48Z"
    - latency: 987.785µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:51:48Z"
    - latency: 1.680193ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:51:48Z"
    - latency: 1.000628ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:50:48Z"
    - latency: 1.710209ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:50:48Z"
    - latency: 887.485µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:49:48Z"
    - latency: 2.025254ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:49:48Z"
kind: List
metadata:
  resourceVersion: ""