apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:39:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-161-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-161.us-east-2.compute.internal
      uid: 19a845a7-ff95-43ab-9a07-ec58be25d021
    resourceVersion: "182890"
    uid: 426100c5-1297-4372-8b1e-10b8f505b070
  spec:
    sourcePod: network-check-source-6f78d59f99-fhbw2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:46:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.20115ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:35:05Z"
    - latency: 1.155509ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:34:05Z"
    - latency: 1.262659ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:33:05Z"
    - latency: 1.676066ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:32:05Z"
    - latency: 2.404955ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:31:05Z"
    - latency: 2.960721ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:30:05Z"
    - latency: 1.508679ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:29:05Z"
    - latency: 1.595502ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:28:05Z"
    - latency: 1.497233ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:27:05Z"
    - latency: 3.609518ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:26:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:39:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-161-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-161.us-east-2.compute.internal
      uid: 19a845a7-ff95-43ab-9a07-ec58be25d021
    resourceVersion: "178258"
    uid: d56f4915-efd0-4596-807f-492f323e2571
  spec:
    sourcePod: network-check-source-6f78d59f99-fhbw2
    targetEndpoint: a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:45:05Z"
      message: 'load-balancer-api-external: tcp connection to a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.371497ms
      message: 'load-balancer-api-external: tcp connection to a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:33:05Z"
    - latency: 7.996374ms
      message: 'load-balancer-api-external: resolved host name a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:33:05Z"
    - latency: 6.419171ms
      message: 'load-balancer-api-external: tcp connection to a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:32:05Z"
    - latency: 8.096534ms
      message: 'load-balancer-api-external: resolved host name a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:32:05Z"
    - latency: 5.907611ms
      message: 'load-balancer-api-external: tcp connection to a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:31:05Z"
    - latency: 6.924712ms
      message: 'load-balancer-api-external: resolved host name a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:31:05Z"
    - latency: 5.771393ms
      message: 'load-balancer-api-external: tcp connection to a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:30:05Z"
    - latency: 10.813013ms
      message: 'load-balancer-api-external: resolved host name a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:30:05Z"
    - latency: 5.714964ms
      message: 'load-balancer-api-external: tcp connection to a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:29:05Z"
    - latency: 9.308241ms
      message: 'load-balancer-api-external: resolved host name a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:29:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:39:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-161-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-161.us-east-2.compute.internal
      uid: 19a845a7-ff95-43ab-9a07-ec58be25d021
    resourceVersion: "178259"
    uid: 1392d2d1-ec3d-4791-b94f-b7ffa61c67a7
  spec:
    sourcePod: network-check-source-6f78d59f99-fhbw2
    targetEndpoint: a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:45:05Z"
      message: 'load-balancer-api-internal: tcp connection to a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.399294ms
      message: 'load-balancer-api-internal: tcp connection to a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:33:05Z"
    - latency: 7.900077ms
      message: 'load-balancer-api-internal: resolved host name a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:33:05Z"
    - latency: 6.404367ms
      message: 'load-balancer-api-internal: tcp connection to a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:32:05Z"
    - latency: 8.240452ms
      message: 'load-balancer-api-internal: resolved host name a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:32:05Z"
    - latency: 5.996166ms
      message: 'load-balancer-api-internal: tcp connection to a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:31:05Z"
    - latency: 6.847204ms
      message: 'load-balancer-api-internal: resolved host name a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:31:05Z"
    - latency: 6.125773ms
      message: 'load-balancer-api-internal: tcp connection to a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:30:05Z"
    - latency: 10.857032ms
      message: 'load-balancer-api-internal: resolved host name a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:30:05Z"
    - latency: 5.72112ms
      message: 'load-balancer-api-internal: tcp connection to a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:29:05Z"
    - latency: 9.096162ms
      message: 'load-balancer-api-internal: resolved host name a2efc7c1b6e1441faabe279557e6d3e8-9dd1385143d0d342.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:29:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:39:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-161-to-network-check-target-ip-10-0-128-161
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-161.us-east-2.compute.internal
      uid: 19a845a7-ff95-43ab-9a07-ec58be25d021
    resourceVersion: "182887"
    uid: 9c3b3210-874d-4b3a-bafb-5299dd55d460
  spec:
    sourcePod: network-check-source-6f78d59f99-fhbw2
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:46:05Z"
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.032182ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:35:05Z"
    - latency: 997.143µs
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:34:05Z"
    - latency: 1.101208ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:33:05Z"
    - latency: 1.604694ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:32:05Z"
    - latency: 1.676098ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:31:05Z"
    - latency: 3.17776ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:30:05Z"
    - latency: 1.697595ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:29:05Z"
    - latency: 1.141057ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:28:05Z"
    - latency: 1.106408ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:27:05Z"
    - latency: 1.350191ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:26:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:39:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-161-to-network-check-target-ip-10-0-130-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-161.us-east-2.compute.internal
      uid: 19a845a7-ff95-43ab-9a07-ec58be25d021
    resourceVersion: "182888"
    uid: 2cfa3c35-cccc-43b8-bf62-702df84d4454
  spec:
    sourcePod: network-check-source-6f78d59f99-fhbw2
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:46:05Z"
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.797804ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:35:05Z"
    - latency: 2.314392ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:34:05Z"
    - latency: 2.420035ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:33:05Z"
    - latency: 3.027907ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:32:05Z"
    - latency: 4.435351ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:31:05Z"
    - latency: 3.491854ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:30:05Z"
    - latency: 3.378897ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:29:05Z"
    - latency: 2.532669ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:28:05Z"
    - latency: 15.809209ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:27:05Z"
    - latency: 2.681935ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:26:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:39:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-161-to-network-check-target-ip-10-0-135-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-161.us-east-2.compute.internal
      uid: 19a845a7-ff95-43ab-9a07-ec58be25d021
    resourceVersion: "182889"
    uid: 4cd9f848-092a-4098-905a-eac462d15186
  spec:
    sourcePod: network-check-source-6f78d59f99-fhbw2
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:46:05Z"
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.696243ms
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:35:05Z"
    - latency: 2.848527ms
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:34:05Z"
    - latency: 3.190444ms
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:33:05Z"
    - latency: 2.944547ms
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:32:05Z"
    - latency: 2.992173ms
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:31:05Z"
    - latency: 4.689814ms
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:30:05Z"
    - latency: 3.404017ms
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:29:05Z"
    - latency: 2.55652ms
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:28:05Z"
    - latency: 2.278082ms
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:27:05Z"
    - latency: 2.810756ms
      message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:26:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:39:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-161-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-161.us-east-2.compute.internal
      uid: 19a845a7-ff95-43ab-9a07-ec58be25d021
    resourceVersion: "178257"
    uid: e223c433-f3f4-4987-af4b-f0378e3762a3
  spec:
    sourcePod: network-check-source-6f78d59f99-fhbw2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:45:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.172988ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:33:05Z"
    - latency: 2.317482ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:33:05Z"
    - latency: 1.272025ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:32:05Z"
    - latency: 1.998584ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:32:05Z"
    - latency: 1.107156ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:31:05Z"
    - latency: 2.529226ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:31:05Z"
    - latency: 1.379285ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:30:05Z"
    - latency: 3.882854ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:30:05Z"
    - latency: 1.089451ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:29:05Z"
    - latency: 2.518601ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:29:05Z"
kind: List
metadata:
  resourceVersion: ""