apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-123-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-123.ec2.internal
      uid: cae14a83-3893-48d3-9efc-2dbe66abbf7e
    resourceVersion: "40816"
    uid: 9969ea15-4a92-4ade-9a67-630b7cabbd68
  spec:
    sourcePod: network-check-source-685456655f-k5hjh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:29:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.061715ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:11:45Z"
    - latency: 1.152754ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:10:45Z"
    - latency: 799.035µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:09:45Z"
    - latency: 1.005004ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:08:45Z"
    - latency: 817.063µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:07:45Z"
    - latency: 1.043239ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:06:45Z"
    - latency: 933.038µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:05:45Z"
    - latency: 939.521µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:04:45Z"
    - latency: 1.072067ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:03:45Z"
    - latency: 926.26µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:02:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-123-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-123.ec2.internal
      uid: cae14a83-3893-48d3-9efc-2dbe66abbf7e
    resourceVersion: "40326"
    uid: c03c3cdc-27aa-4a22-8b16-8930bd77a4cd
  spec:
    sourcePod: network-check-source-685456655f-k5hjh
    targetEndpoint: af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:28:45Z"
      message: 'load-balancer-api-external: tcp connection to af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.899869ms
      message: 'load-balancer-api-external: tcp connection to af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:10:45Z"
    - latency: 6.530625ms
      message: 'load-balancer-api-external: resolved host name af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:10:45Z"
    - latency: 5.794557ms
      message: 'load-balancer-api-external: tcp connection to af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:09:45Z"
    - latency: 6.20574ms
      message: 'load-balancer-api-external: resolved host name af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:09:45Z"
    - latency: 5.50741ms
      message: 'load-balancer-api-external: tcp connection to af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:08:45Z"
    - latency: 7.23212ms
      message: 'load-balancer-api-external: resolved host name af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:08:45Z"
    - latency: 6.176693ms
      message: 'load-balancer-api-external: tcp connection to af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:07:45Z"
    - latency: 6.71181ms
      message: 'load-balancer-api-external: resolved host name af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:07:45Z"
    - latency: 4.841719ms
      message: 'load-balancer-api-external: tcp connection to af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:06:45Z"
    - latency: 7.816781ms
      message: 'load-balancer-api-external: resolved host name af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:06:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-123-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-123.ec2.internal
      uid: cae14a83-3893-48d3-9efc-2dbe66abbf7e
    resourceVersion: "40325"
    uid: 3b798fcf-f989-4efb-83d4-7ad0bf173f50
  spec:
    sourcePod: network-check-source-685456655f-k5hjh
    targetEndpoint: af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:28:45Z"
      message: 'load-balancer-api-internal: tcp connection to af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.950141ms
      message: 'load-balancer-api-internal: tcp connection to af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:10:45Z"
    - latency: 6.470603ms
      message: 'load-balancer-api-internal: resolved host name af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:10:45Z"
    - latency: 5.799994ms
      message: 'load-balancer-api-internal: tcp connection to af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:09:45Z"
    - latency: 6.159468ms
      message: 'load-balancer-api-internal: resolved host name af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:09:45Z"
    - latency: 4.835515ms
      message: 'load-balancer-api-internal: tcp connection to af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:08:45Z"
    - latency: 7.212482ms
      message: 'load-balancer-api-internal: resolved host name af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:08:45Z"
    - latency: 6.134336ms
      message: 'load-balancer-api-internal: tcp connection to af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:07:45Z"
    - latency: 6.796852ms
      message: 'load-balancer-api-internal: resolved host name af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:07:45Z"
    - latency: 7.340284ms
      message: 'load-balancer-api-internal: tcp connection to af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:06:45Z"
    - latency: 7.727766ms
      message: 'load-balancer-api-internal: resolved host name af4baad54c94b4ac0a1fe08b1b5f0f0f-f60c9d306453ccec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:06:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-123-to-network-check-target-ip-10-0-128-91
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-123.ec2.internal
      uid: cae14a83-3893-48d3-9efc-2dbe66abbf7e
    resourceVersion: "40814"
    uid: 70dd2145-34a0-4997-9b90-6b336592510a
  spec:
    sourcePod: network-check-source-685456655f-k5hjh
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:29:45Z"
      message: 'network-check-target-ip-10-0-128-91: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.882397ms
      message: 'network-check-target-ip-10-0-128-91: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:11:45Z"
    - latency: 1.749203ms
      message: 'network-check-target-ip-10-0-128-91: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:10:45Z"
    - latency: 1.697554ms
      message: 'network-check-target-ip-10-0-128-91: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:09:45Z"
    - latency: 1.956492ms
      message: 'network-check-target-ip-10-0-128-91: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:08:45Z"
    - latency: 1.652558ms
      message: 'network-check-target-ip-10-0-128-91: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:07:45Z"
    - latency: 1.910937ms
      message: 'network-check-target-ip-10-0-128-91: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:06:45Z"
    - latency: 1.695388ms
      message: 'network-check-target-ip-10-0-128-91: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:05:45Z"
    - latency: 1.784778ms
      message: 'network-check-target-ip-10-0-128-91: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:04:45Z"
    - latency: 1.882907ms
      message: 'network-check-target-ip-10-0-128-91: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:03:45Z"
    - latency: 1.827839ms
      message: 'network-check-target-ip-10-0-128-91: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:02:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-123-to-network-check-target-ip-10-0-137-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-123.ec2.internal
      uid: cae14a83-3893-48d3-9efc-2dbe66abbf7e
    resourceVersion: "40815"
    uid: 8e8c18ab-9d86-4261-9f2a-7713582eb0f5
  spec:
    sourcePod: network-check-source-685456655f-k5hjh
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:29:45Z"
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.358616ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:11:45Z"
    - latency: 2.165679ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:10:45Z"
    - latency: 2.264873ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:09:45Z"
    - latency: 2.713353ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:08:45Z"
    - latency: 1.750792ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:07:45Z"
    - latency: 2.533547ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:06:45Z"
    - latency: 2.323853ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:05:45Z"
    - latency: 2.154004ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:04:45Z"
    - latency: 2.441301ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:03:45Z"
    - latency: 1.986712ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:02:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-123-to-network-check-target-ip-10-0-138-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-123.ec2.internal
      uid: cae14a83-3893-48d3-9efc-2dbe66abbf7e
    resourceVersion: "40813"
    uid: 45cd1321-1d50-46fd-9551-86f1824c2e18
  spec:
    sourcePod: network-check-source-685456655f-k5hjh
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:29:45Z"
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.055632ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:11:45Z"
    - latency: 1.017742ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:10:45Z"
    - latency: 854.971µs
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:09:45Z"
    - latency: 1.432601ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:08:45Z"
    - latency: 870.607µs
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:07:45Z"
    - latency: 876.554µs
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:06:45Z"
    - latency: 769.977µs
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:05:45Z"
    - latency: 1.039882ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:04:45Z"
    - latency: 955.733µs
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:03:45Z"
    - latency: 1.206748ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:02:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-123-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-123.ec2.internal
      uid: cae14a83-3893-48d3-9efc-2dbe66abbf7e
    resourceVersion: "40324"
    uid: 8b34ffd9-dd20-4efb-90c8-f1e8a139438e
  spec:
    sourcePod: network-check-source-685456655f-k5hjh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:28:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 919.357µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:10:45Z"
    - latency: 1.760967ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:10:45Z"
    - latency: 998.585µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:09:45Z"
    - latency: 1.795271ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:09:45Z"
    - latency: 868.834µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:08:45Z"
    - latency: 1.79305ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:08:45Z"
    - latency: 818.3µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:07:45Z"
    - latency: 1.921512ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:07:45Z"
    - latency: 800.142µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:06:45Z"
    - latency: 1.934941ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:06:45Z"
kind: List
metadata:
  resourceVersion: ""