apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:00:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-209-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-209.ec2.internal
      uid: fd812f97-c646-4862-a444-6275cbc6408f
    resourceVersion: "23173"
    uid: d17a8c2b-c088-44b6-8d7c-70358ff2465a
  spec:
    sourcePod: network-check-source-7cbc45fddc-j2gss
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:07:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.297392ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:28Z"
    - latency: 1.264515ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:28Z"
    - latency: 960.671µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:28Z"
    - latency: 903.22µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:18:28Z"
    - latency: 967.289µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:17:28Z"
    - latency: 1.198132ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:16:28Z"
    - latency: 1.229373ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:15:28Z"
    - latency: 1.091802ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:14:28Z"
    - latency: 1.078032ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:13:28Z"
    - latency: 1.003104ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:12:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:00:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-209-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-209.ec2.internal
      uid: fd812f97-c646-4862-a444-6275cbc6408f
    resourceVersion: "21668"
    uid: 4c9a2b51-2520-4de1-bee8-788ad4bd4d5f
  spec:
    sourcePod: network-check-source-7cbc45fddc-j2gss
    targetEndpoint: a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:06:28Z"
      message: 'load-balancer-api-external: tcp connection to a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.317698ms
      message: 'load-balancer-api-external: tcp connection to a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:18:28Z"
    - latency: 6.770705ms
      message: 'load-balancer-api-external: resolved host name a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:18:28Z"
    - latency: 5.297403ms
      message: 'load-balancer-api-external: tcp connection to a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:17:28Z"
    - latency: 7.690164ms
      message: 'load-balancer-api-external: resolved host name a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:17:28Z"
    - latency: 5.052789ms
      message: 'load-balancer-api-external: tcp connection to a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:16:28Z"
    - latency: 6.592801ms
      message: 'load-balancer-api-external: resolved host name a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:16:28Z"
    - latency: 5.15445ms
      message: 'load-balancer-api-external: tcp connection to a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:15:28Z"
    - latency: 6.563819ms
      message: 'load-balancer-api-external: resolved host name a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:15:28Z"
    - latency: 5.096737ms
      message: 'load-balancer-api-external: tcp connection to a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:14:28Z"
    - latency: 7.43393ms
      message: 'load-balancer-api-external: resolved host name a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:14:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:00:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-209-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-209.ec2.internal
      uid: fd812f97-c646-4862-a444-6275cbc6408f
    resourceVersion: "21667"
    uid: 1158b225-1797-4b8c-b70d-b269f3df04a3
  spec:
    sourcePod: network-check-source-7cbc45fddc-j2gss
    targetEndpoint: a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:06:28Z"
      message: 'load-balancer-api-internal: tcp connection to a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.900405ms
      message: 'load-balancer-api-internal: tcp connection to a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:18:28Z"
    - latency: 6.831286ms
      message: 'load-balancer-api-internal: resolved host name a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:18:28Z"
    - latency: 5.15075ms
      message: 'load-balancer-api-internal: tcp connection to a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:17:28Z"
    - latency: 7.594799ms
      message: 'load-balancer-api-internal: resolved host name a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:17:28Z"
    - latency: 5.02236ms
      message: 'load-balancer-api-internal: tcp connection to a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:16:28Z"
    - latency: 6.636665ms
      message: 'load-balancer-api-internal: resolved host name a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:16:28Z"
    - latency: 5.069554ms
      message: 'load-balancer-api-internal: tcp connection to a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:15:28Z"
    - latency: 6.416165ms
      message: 'load-balancer-api-internal: resolved host name a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:15:28Z"
    - latency: 5.157681ms
      message: 'load-balancer-api-internal: tcp connection to a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:14:28Z"
    - latency: 7.401859ms
      message: 'load-balancer-api-internal: resolved host name a9fa84e90973c412899cf83e0fc51972-6afd5615cbb7efcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:14:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:00:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-209-to-network-check-target-ip-10-0-134-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-209.ec2.internal
      uid: fd812f97-c646-4862-a444-6275cbc6408f
    resourceVersion: "23170"
    uid: 10545027-344a-42b4-9704-1b6ad1502180
  spec:
    sourcePod: network-check-source-7cbc45fddc-j2gss
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:07:28Z"
      message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.727195ms
      message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:28Z"
    - latency: 914.522µs
      message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:28Z"
    - latency: 787.669µs
      message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:28Z"
    - latency: 1.05322ms
      message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:18:28Z"
    - latency: 829.992µs
      message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:17:28Z"
    - latency: 765.821µs
      message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:16:28Z"
    - latency: 926.531µs
      message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:15:28Z"
    - latency: 775.281µs
      message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:14:28Z"
    - latency: 791.289µs
      message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:13:28Z"
    - latency: 1.103883ms
      message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:12:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:00:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-209-to-network-check-target-ip-10-0-141-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-209.ec2.internal
      uid: fd812f97-c646-4862-a444-6275cbc6408f
    resourceVersion: "23172"
    uid: 4e285c45-04a2-4319-994f-736340de4470
  spec:
    sourcePod: network-check-source-7cbc45fddc-j2gss
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:07:28Z"
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.304307ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:28Z"
    - latency: 2.495237ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:28Z"
    - latency: 2.287335ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:28Z"
    - latency: 2.334544ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:18:28Z"
    - latency: 2.426089ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:17:28Z"
    - latency: 2.507458ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:16:28Z"
    - latency: 2.358618ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:15:28Z"
    - latency: 2.11252ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:14:28Z"
    - latency: 2.257652ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:13:28Z"
    - latency: 2.473106ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:12:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:00:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-209-to-network-check-target-ip-10-0-143-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-209.ec2.internal
      uid: fd812f97-c646-4862-a444-6275cbc6408f
    resourceVersion: "23171"
    uid: 6b072bbb-6e41-4f72-bdb7-f8d1ec0d7444
  spec:
    sourcePod: network-check-source-7cbc45fddc-j2gss
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:07:28Z"
      message: 'network-check-target-ip-10-0-143-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.328663ms
      message: 'network-check-target-ip-10-0-143-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:28Z"
    - latency: 2.334401ms
      message: 'network-check-target-ip-10-0-143-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:28Z"
    - latency: 2.523645ms
      message: 'network-check-target-ip-10-0-143-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:28Z"
    - latency: 2.042814ms
      message: 'network-check-target-ip-10-0-143-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:18:28Z"
    - latency: 2.161926ms
      message: 'network-check-target-ip-10-0-143-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:17:28Z"
    - latency: 2.503566ms
      message: 'network-check-target-ip-10-0-143-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:16:28Z"
    - latency: 2.378608ms
      message: 'network-check-target-ip-10-0-143-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:15:28Z"
    - latency: 2.628151ms
      message: 'network-check-target-ip-10-0-143-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:14:28Z"
    - latency: 2.223414ms
      message: 'network-check-target-ip-10-0-143-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:13:28Z"
    - latency: 2.606836ms
      message: 'network-check-target-ip-10-0-143-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:12:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:00:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-209-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-209.ec2.internal
      uid: fd812f97-c646-4862-a444-6275cbc6408f
    resourceVersion: "21666"
    uid: 73ed8349-b8c6-4738-8647-e844a824060b
  spec:
    sourcePod: network-check-source-7cbc45fddc-j2gss
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:06:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 983.17µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:18:28Z"
    - latency: 1.795142ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:18:28Z"
    - latency: 1.249119ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:17:28Z"
    - latency: 2.074896ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:17:28Z"
    - latency: 1.390913ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:16:28Z"
    - latency: 1.820077ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:16:28Z"
    - latency: 824.918µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:15:28Z"
    - latency: 1.932485ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:15:28Z"
    - latency: 1.054626ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:14:28Z"
    - latency: 1.990953ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:14:28Z"
kind: List
metadata:
  resourceVersion: ""