apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-121-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-121.ec2.internal
      uid: 67ff24ce-3be0-4f72-ad73-5ff3f29e46e6
    resourceVersion: "89603"
    uid: 54d635a4-1f1c-4138-8fdb-ed79ab8971f8
  spec:
    sourcePod: network-check-source-7d88cb55d8-kp7k8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:28:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.164974ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:24:51Z"
    - latency: 772.306µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:23:51Z"
    - latency: 1.400913ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:22:51Z"
    - latency: 1.056558ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:21:51Z"
    - latency: 938.935µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:20:51Z"
    - latency: 848.349µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:19:51Z"
    - latency: 916.352µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:18:51Z"
    - latency: 952.592µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:17:51Z"
    - latency: 967.67µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:16:51Z"
    - latency: 1.032875ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:15:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-121-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-121.ec2.internal
      uid: 67ff24ce-3be0-4f72-ad73-5ff3f29e46e6
    resourceVersion: "95772"
    uid: 49590729-feff-4084-98a3-aa13eefaaa56
  spec:
    sourcePod: network-check-source-7d88cb55d8-kp7k8
    targetEndpoint: ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:27:51Z"
      message: 'load-balancer-api-external: tcp connection to ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.458527ms
      message: 'load-balancer-api-external: tcp connection to ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:27:51Z"
    - latency: 8.665864ms
      message: 'load-balancer-api-external: resolved host name ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:27:51Z"
    - latency: 5.219418ms
      message: 'load-balancer-api-external: tcp connection to ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:26:51Z"
    - latency: 7.569018ms
      message: 'load-balancer-api-external: resolved host name ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:26:51Z"
    - latency: 4.697035ms
      message: 'load-balancer-api-external: tcp connection to ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:25:51Z"
    - latency: 7.255717ms
      message: 'load-balancer-api-external: resolved host name ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:25:51Z"
    - latency: 5.070482ms
      message: 'load-balancer-api-external: tcp connection to ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:24:51Z"
    - latency: 8.965368ms
      message: 'load-balancer-api-external: resolved host name ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:24:51Z"
    - latency: 6.307503ms
      message: 'load-balancer-api-external: tcp connection to ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:23:51Z"
    - latency: 7.283889ms
      message: 'load-balancer-api-external: resolved host name ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:23:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-121-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-121.ec2.internal
      uid: 67ff24ce-3be0-4f72-ad73-5ff3f29e46e6
    resourceVersion: "95773"
    uid: babc482d-962f-4880-9631-52a453fd6383
  spec:
    sourcePod: network-check-source-7d88cb55d8-kp7k8
    targetEndpoint: ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:27:51Z"
      message: 'load-balancer-api-internal: tcp connection to ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.832442ms
      message: 'load-balancer-api-internal: tcp connection to ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:27:51Z"
    - latency: 8.766532ms
      message: 'load-balancer-api-internal: resolved host name ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:27:51Z"
    - latency: 5.177549ms
      message: 'load-balancer-api-internal: tcp connection to ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:26:51Z"
    - latency: 7.605178ms
      message: 'load-balancer-api-internal: resolved host name ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:26:51Z"
    - latency: 4.639135ms
      message: 'load-balancer-api-internal: tcp connection to ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:25:51Z"
    - latency: 7.313654ms
      message: 'load-balancer-api-internal: resolved host name ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:25:51Z"
    - latency: 5.160049ms
      message: 'load-balancer-api-internal: tcp connection to ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:24:51Z"
    - latency: 8.928269ms
      message: 'load-balancer-api-internal: resolved host name ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:24:51Z"
    - latency: 4.185977ms
      message: 'load-balancer-api-internal: tcp connection to ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:23:51Z"
    - latency: 7.313042ms
      message: 'load-balancer-api-internal: resolved host name ae4f654c581a245b189dc3e07d5a5966-1c5c9b8715c5aa25.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:23:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-121-to-network-check-target-ip-10-0-130-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-121.ec2.internal
      uid: 67ff24ce-3be0-4f72-ad73-5ff3f29e46e6
    resourceVersion: "89601"
    uid: c7e37727-77b1-45e4-99ac-10468e6a4ee1
  spec:
    sourcePod: network-check-source-7d88cb55d8-kp7k8
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:28:51Z"
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.300961ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:24:51Z"
    - latency: 2.502795ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:23:51Z"
    - latency: 2.03585ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:22:51Z"
    - latency: 2.203308ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:21:51Z"
    - latency: 2.027515ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:20:51Z"
    - latency: 1.867135ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:19:51Z"
    - latency: 2.38875ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:18:51Z"
    - latency: 2.290232ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:17:51Z"
    - latency: 2.301441ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:16:51Z"
    - latency: 2.49814ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:15:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-121-to-network-check-target-ip-10-0-131-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-121.ec2.internal
      uid: 67ff24ce-3be0-4f72-ad73-5ff3f29e46e6
    resourceVersion: "89600"
    uid: 2878ec65-9e63-447f-8582-ca7b079d0e73
  spec:
    sourcePod: network-check-source-7d88cb55d8-kp7k8
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:28:51Z"
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 989.426µs
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:24:51Z"
    - latency: 866.254µs
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:23:51Z"
    - latency: 815.966µs
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:22:51Z"
    - latency: 861.304µs
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:21:51Z"
    - latency: 979.512µs
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:20:51Z"
    - latency: 818.137µs
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:19:51Z"
    - latency: 1.188024ms
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:18:51Z"
    - latency: 922.145µs
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:17:51Z"
    - latency: 1.091585ms
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:16:51Z"
    - latency: 1.025785ms
      message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:15:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-121-to-network-check-target-ip-10-0-141-50
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-121.ec2.internal
      uid: 67ff24ce-3be0-4f72-ad73-5ff3f29e46e6
    resourceVersion: "89602"
    uid: 425391f6-504c-48d4-836e-84414c6aad5d
  spec:
    sourcePod: network-check-source-7d88cb55d8-kp7k8
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:28:51Z"
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.382377ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:24:51Z"
    - latency: 1.959027ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:23:51Z"
    - latency: 1.947567ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:22:51Z"
    - latency: 2.240263ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:21:51Z"
    - latency: 2.054791ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:20:51Z"
    - latency: 2.100023ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:19:51Z"
    - latency: 2.257955ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:18:51Z"
    - latency: 2.178434ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:17:51Z"
    - latency: 2.18128ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:16:51Z"
    - latency: 2.097821ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:15:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-121-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-121.ec2.internal
      uid: 67ff24ce-3be0-4f72-ad73-5ff3f29e46e6
    resourceVersion: "95771"
    uid: 3407071b-a05c-42d0-bcb6-50fbdda326f4
  spec:
    sourcePod: network-check-source-7d88cb55d8-kp7k8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:27:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.095389ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:27:51Z"
    - latency: 1.898635ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:27:51Z"
    - latency: 1.715249ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:26:51Z"
    - latency: 2.018449ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:26:51Z"
    - latency: 810.191µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:25:51Z"
    - latency: 2.252971ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:25:51Z"
    - latency: 1.023296ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:24:51Z"
    - latency: 1.947927ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:24:51Z"
    - latency: 928.963µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:23:51Z"
    - latency: 1.746094ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:23:51Z"
kind: List
metadata:
  resourceVersion: ""