apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:25:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-254-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-254.ec2.internal
      uid: 5ea58cee-1aa3-4854-a23f-8ba96af1ffa8
    resourceVersion: "77727"
    uid: b0840491-eb2b-43d1-8f82-6893a5ddd80f
  spec:
    sourcePod: network-check-source-7cbc45fddc-5q6n6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:32:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.033492ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:28:20Z"
    - latency: 1.057351ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:27:20Z"
    - latency: 1.077408ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:26:20Z"
    - latency: 983.203µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:25:20Z"
    - latency: 933.691µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:24:20Z"
    - latency: 905.47µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:23:20Z"
    - latency: 1.140247ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:22:20Z"
    - latency: 1.38043ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:21:20Z"
    - latency: 1.04123ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:20:20Z"
    - latency: 906.842µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:19:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:25:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-254-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-254.ec2.internal
      uid: 5ea58cee-1aa3-4854-a23f-8ba96af1ffa8
    resourceVersion: "74652"
    uid: 75c741c0-0694-4009-aa1b-bca2f93a3bb4
  spec:
    sourcePod: network-check-source-7cbc45fddc-5q6n6
    targetEndpoint: a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:31:20Z"
      message: 'load-balancer-api-external: tcp connection to a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.402344ms
      message: 'load-balancer-api-external: tcp connection to a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:25:20Z"
    - latency: 8.973301ms
      message: 'load-balancer-api-external: resolved host name a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:25:20Z"
    - latency: 4.313668ms
      message: 'load-balancer-api-external: tcp connection to a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:24:20Z"
    - latency: 10.035894ms
      message: 'load-balancer-api-external: resolved host name a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:24:20Z"
    - latency: 4.728383ms
      message: 'load-balancer-api-external: tcp connection to a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:23:20Z"
    - latency: 12.876147ms
      message: 'load-balancer-api-external: resolved host name a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:23:20Z"
    - latency: 5.470742ms
      message: 'load-balancer-api-external: tcp connection to a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:22:20Z"
    - latency: 9.646901ms
      message: 'load-balancer-api-external: resolved host name a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:22:20Z"
    - latency: 5.398166ms
      message: 'load-balancer-api-external: tcp connection to a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:21:20Z"
    - latency: 9.862979ms
      message: 'load-balancer-api-external: resolved host name a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:21:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:25:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-254-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-254.ec2.internal
      uid: 5ea58cee-1aa3-4854-a23f-8ba96af1ffa8
    resourceVersion: "74653"
    uid: 45bebc0f-a898-4428-88b2-4e9025236d93
  spec:
    sourcePod: network-check-source-7cbc45fddc-5q6n6
    targetEndpoint: a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:31:20Z"
      message: 'load-balancer-api-internal: tcp connection to a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.371645ms
      message: 'load-balancer-api-internal: tcp connection to a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:25:20Z"
    - latency: 9.087244ms
      message: 'load-balancer-api-internal: resolved host name a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:25:20Z"
    - latency: 4.905295ms
      message: 'load-balancer-api-internal: tcp connection to a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:24:20Z"
    - latency: 10.171157ms
      message: 'load-balancer-api-internal: resolved host name a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:24:20Z"
    - latency: 4.761046ms
      message: 'load-balancer-api-internal: tcp connection to a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:23:20Z"
    - latency: 12.941771ms
      message: 'load-balancer-api-internal: resolved host name a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:23:20Z"
    - latency: 5.42515ms
      message: 'load-balancer-api-internal: tcp connection to a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:22:20Z"
    - latency: 9.755218ms
      message: 'load-balancer-api-internal: resolved host name a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:22:20Z"
    - latency: 5.336158ms
      message: 'load-balancer-api-internal: tcp connection to a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:21:20Z"
    - latency: 9.829854ms
      message: 'load-balancer-api-internal: resolved host name a3e9b46b92b594a979adb5c0bb3ce58c-b90bb326aaeaeadb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:21:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:25:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-254-to-network-check-target-ip-10-0-131-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-254.ec2.internal
      uid: 5ea58cee-1aa3-4854-a23f-8ba96af1ffa8
    resourceVersion: "77726"
    uid: bcd40161-03c3-4f5a-8bb9-015d1375dcd3
  spec:
    sourcePod: network-check-source-7cbc45fddc-5q6n6
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:32:20Z"
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.563341ms
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:28:20Z"
    - latency: 2.337847ms
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:27:20Z"
    - latency: 2.583831ms
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:26:20Z"
    - latency: 3.141083ms
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:25:20Z"
    - latency: 3.115455ms
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:24:20Z"
    - latency: 2.670046ms
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:23:20Z"
    - latency: 2.904152ms
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:22:20Z"
    - latency: 2.249147ms
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:21:20Z"
    - latency: 2.604539ms
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:20:20Z"
    - latency: 2.163242ms
      message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:19:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:25:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-254-to-network-check-target-ip-10-0-134-254
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-254.ec2.internal
      uid: 5ea58cee-1aa3-4854-a23f-8ba96af1ffa8
    resourceVersion: "77724"
    uid: 2ca8f436-ef8c-405c-aacc-8212cea83334
  spec:
    sourcePod: network-check-source-7cbc45fddc-5q6n6
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:32:20Z"
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.1539ms
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:28:20Z"
    - latency: 1.315243ms
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:27:20Z"
    - latency: 1.336344ms
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:26:20Z"
    - latency: 1.423608ms
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:25:20Z"
    - latency: 1.027491ms
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:24:20Z"
    - latency: 1.676528ms
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:23:20Z"
    - latency: 1.081033ms
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:22:20Z"
    - latency: 1.050205ms
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:21:20Z"
    - latency: 923.259µs
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:20:20Z"
    - latency: 885.366µs
      message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:19:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:25:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-254-to-network-check-target-ip-10-0-140-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-254.ec2.internal
      uid: 5ea58cee-1aa3-4854-a23f-8ba96af1ffa8
    resourceVersion: "77725"
    uid: a2ce3502-2d2c-4249-a1a0-82e7fa7e53cc
  spec:
    sourcePod: network-check-source-7cbc45fddc-5q6n6
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:32:20Z"
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.329207ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:28:20Z"
    - latency: 2.412545ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:27:20Z"
    - latency: 2.534284ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:26:20Z"
    - latency: 2.741522ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:25:20Z"
    - latency: 2.497616ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:24:20Z"
    - latency: 2.425622ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:23:20Z"
    - latency: 2.440854ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:22:20Z"
    - latency: 2.31898ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:21:20Z"
    - latency: 2.44571ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:20:20Z"
    - latency: 2.324281ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:19:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:25:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-254-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-254.ec2.internal
      uid: 5ea58cee-1aa3-4854-a23f-8ba96af1ffa8
    resourceVersion: "74651"
    uid: 2b9190b1-dc4b-449b-b5ed-21ee856a11d5
  spec:
    sourcePod: network-check-source-7cbc45fddc-5q6n6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:31:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 957.119µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:25:20Z"
    - latency: 1.722467ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:25:20Z"
    - latency: 1.110175ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:24:20Z"
    - latency: 2.468643ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:24:20Z"
    - latency: 998.53µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:23:20Z"
    - latency: 1.870785ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:23:20Z"
    - latency: 1.017786ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:22:20Z"
    - latency: 1.82077ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:22:20Z"
    - latency: 1.12658ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:21:20Z"
    - latency: 1.864106ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:21:20Z"
kind: List
metadata:
  resourceVersion: ""