apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T09:22:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-141-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-141.ec2.internal
      uid: 5576b302-bedf-4f82-92a5-a8d8ad12a2a0
    resourceVersion: "63955"
    uid: 22e9353e-6fd4-474a-bfc5-d8d5d758fa9b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-c6vsv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T09:29:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 803.162µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:04:04Z"
    - latency: 945.269µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:03:04Z"
    - latency: 1.086125ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:02:04Z"
    - latency: 1.068194ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:01:04Z"
    - latency: 1.51467ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:00:04Z"
    - latency: 1.268429ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:59:04Z"
    - latency: 1.172338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:58:04Z"
    - latency: 1.067886ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:57:04Z"
    - latency: 923.414µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:56:04Z"
    - latency: 1.109634ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:55:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T09:22:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-141-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-141.ec2.internal
      uid: 5576b302-bedf-4f82-92a5-a8d8ad12a2a0
    resourceVersion: "63957"
    uid: 23e4df82-45d7-41cd-9baa-5c2214b767cf
  spec:
    sourcePod: network-check-source-7bc5b6bf85-c6vsv
    targetEndpoint: a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T09:28:04Z"
      message: 'load-balancer-api-external: tcp connection to a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.13403ms
      message: 'load-balancer-api-external: tcp connection to a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:04:04Z"
    - latency: 8.851486ms
      message: 'load-balancer-api-external: resolved host name a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T10:04:04Z"
    - latency: 4.389047ms
      message: 'load-balancer-api-external: tcp connection to a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:03:04Z"
    - latency: 9.076249ms
      message: 'load-balancer-api-external: resolved host name a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T10:03:04Z"
    - latency: 5.464563ms
      message: 'load-balancer-api-external: tcp connection to a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:02:04Z"
    - latency: 8.809386ms
      message: 'load-balancer-api-external: resolved host name a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T10:02:04Z"
    - latency: 5.179896ms
      message: 'load-balancer-api-external: tcp connection to a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:01:04Z"
    - latency: 8.67286ms
      message: 'load-balancer-api-external: resolved host name a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T10:01:04Z"
    - latency: 4.619012ms
      message: 'load-balancer-api-external: tcp connection to a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:00:04Z"
    - latency: 7.062563ms
      message: 'load-balancer-api-external: resolved host name a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T10:00:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T09:22:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-141-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-141.ec2.internal
      uid: 5576b302-bedf-4f82-92a5-a8d8ad12a2a0
    resourceVersion: "63956"
    uid: b2c59f81-def0-4945-badb-98b884d2cd53
  spec:
    sourcePod: network-check-source-7bc5b6bf85-c6vsv
    targetEndpoint: a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T09:28:04Z"
      message: 'load-balancer-api-internal: tcp connection to a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.172076ms
      message: 'load-balancer-api-internal: tcp connection to a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:04:04Z"
    - latency: 8.829087ms
      message: 'load-balancer-api-internal: resolved host name a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T10:04:04Z"
    - latency: 4.435195ms
      message: 'load-balancer-api-internal: tcp connection to a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:03:04Z"
    - latency: 9.03836ms
      message: 'load-balancer-api-internal: resolved host name a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T10:03:04Z"
    - latency: 5.456974ms
      message: 'load-balancer-api-internal: tcp connection to a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:02:04Z"
    - latency: 8.773981ms
      message: 'load-balancer-api-internal: resolved host name a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T10:02:04Z"
    - latency: 5.19274ms
      message: 'load-balancer-api-internal: tcp connection to a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:01:04Z"
    - latency: 8.644781ms
      message: 'load-balancer-api-internal: resolved host name a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T10:01:04Z"
    - latency: 3.889113ms
      message: 'load-balancer-api-internal: tcp connection to a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:00:04Z"
    - latency: 7.007385ms
      message: 'load-balancer-api-internal: resolved host name a4d7cef1f9dc1403f9b43b88e7b52520-d15c59425546c3b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T10:00:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T09:22:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-141-to-network-check-target-ip-10-0-134-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-141.ec2.internal
      uid: 5576b302-bedf-4f82-92a5-a8d8ad12a2a0
    resourceVersion: "63953"
    uid: fc4f88eb-b8ec-42f0-bb18-3fe114cb3e29
  spec:
    sourcePod: network-check-source-7bc5b6bf85-c6vsv
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T09:29:04Z"
      message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.21074ms
      message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:04:04Z"
    - latency: 2.259623ms
      message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:03:04Z"
    - latency: 2.307166ms
      message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:02:04Z"
    - latency: 1.930911ms
      message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:01:04Z"
    - latency: 2.14205ms
      message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:00:04Z"
    - latency: 1.953892ms
      message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:59:04Z"
    - latency: 2.150068ms
      message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:58:04Z"
    - latency: 1.920405ms
      message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:57:04Z"
    - latency: 1.958578ms
      message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:56:04Z"
    - latency: 2.113013ms
      message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:55:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T09:22:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-141-to-network-check-target-ip-10-0-138-138
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-141.ec2.internal
      uid: 5576b302-bedf-4f82-92a5-a8d8ad12a2a0
    resourceVersion: "63954"
    uid: 4b716631-b6cf-4336-a49a-f6ae6ae057d1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-c6vsv
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T09:29:04Z"
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.424204ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:04:04Z"
    - latency: 2.190068ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:03:04Z"
    - latency: 2.381862ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:02:04Z"
    - latency: 2.259593ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:01:04Z"
    - latency: 2.258772ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:00:04Z"
    - latency: 2.159981ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:59:04Z"
    - latency: 2.310549ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:58:04Z"
    - latency: 2.030067ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:57:04Z"
    - latency: 2.11247ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:56:04Z"
    - latency: 2.099001ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:55:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T09:22:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-141-to-network-check-target-ip-10-0-142-141
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-141.ec2.internal
      uid: 5576b302-bedf-4f82-92a5-a8d8ad12a2a0
    resourceVersion: "63951"
    uid: 4728d156-d4a7-45aa-b505-5f0ae7c12c90
  spec:
    sourcePod: network-check-source-7bc5b6bf85-c6vsv
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T09:29:04Z"
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 861.669µs
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:04:04Z"
    - latency: 896.798µs
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:03:04Z"
    - latency: 844.948µs
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:02:04Z"
    - latency: 1.329877ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:01:04Z"
    - latency: 1.000319ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:00:04Z"
    - latency: 865.464µs
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:59:04Z"
    - latency: 862.79µs
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:58:04Z"
    - latency: 1.043566ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:57:04Z"
    - latency: 751.617µs
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:56:04Z"
    - latency: 857.373µs
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T09:55:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T09:22:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-141-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-141.ec2.internal
      uid: 5576b302-bedf-4f82-92a5-a8d8ad12a2a0
    resourceVersion: "63952"
    uid: 840b092e-e1b2-4489-84ce-d4ee7a8fa81b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-c6vsv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T09:28:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 791.974µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:04:04Z"
    - latency: 1.74275ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T10:04:04Z"
    - latency: 1.218332ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:03:04Z"
    - latency: 1.778043ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T10:03:04Z"
    - latency: 747.784µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:02:04Z"
    - latency: 1.756567ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T10:02:04Z"
    - latency: 1.079872ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:01:04Z"
    - latency: 1.702251ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T10:01:04Z"
    - latency: 1.205651ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T10:00:04Z"
    - latency: 1.780822ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T10:00:04Z"
kind: List
metadata:
  resourceVersion: ""