apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T17:51:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-111-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-111.ec2.internal
      uid: 00cc89b9-c60e-4556-927f-4ec115c5896d
    resourceVersion: "30165"
    uid: 63d28b3e-b88b-4ea8-88a1-432ca3001c9d
  spec:
    sourcePod: network-check-source-56d84b9f44-xwprz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T17:58:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.427449ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:05:48Z"
    - latency: 1.214287ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:04:48Z"
    - latency: 1.032293ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:03:48Z"
    - latency: 1.209396ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:02:48Z"
    - latency: 1.033122ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:01:48Z"
    - latency: 1.111247ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:00:48Z"
    - latency: 1.394199ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:59:48Z"
    - latency: 1.11804ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:58:48Z"
    - latency: 1.14482ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:57:48Z"
    - latency: 963.512µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:56:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T17:51:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-111-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-111.ec2.internal
      uid: 00cc89b9-c60e-4556-927f-4ec115c5896d
    resourceVersion: "28616"
    uid: 9db2783b-776f-412c-923e-b145bb129a91
  spec:
    sourcePod: network-check-source-56d84b9f44-xwprz
    targetEndpoint: a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T17:57:48Z"
      message: 'load-balancer-api-external: tcp connection to a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.32942ms
      message: 'load-balancer-api-external: tcp connection to a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:03:48Z"
    - latency: 7.391078ms
      message: 'load-balancer-api-external: resolved host name a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T18:03:48Z"
    - latency: 4.692509ms
      message: 'load-balancer-api-external: tcp connection to a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:02:48Z"
    - latency: 6.913252ms
      message: 'load-balancer-api-external: resolved host name a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T18:02:48Z"
    - latency: 4.742703ms
      message: 'load-balancer-api-external: tcp connection to a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:01:48Z"
    - latency: 8.336712ms
      message: 'load-balancer-api-external: resolved host name a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T18:01:48Z"
    - latency: 4.896871ms
      message: 'load-balancer-api-external: tcp connection to a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:00:48Z"
    - latency: 6.75888ms
      message: 'load-balancer-api-external: resolved host name a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T18:00:48Z"
    - latency: 4.089795ms
      message: 'load-balancer-api-external: tcp connection to a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:59:48Z"
    - latency: 7.827592ms
      message: 'load-balancer-api-external: resolved host name a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T17:59:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T17:51:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-111-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-111.ec2.internal
      uid: 00cc89b9-c60e-4556-927f-4ec115c5896d
    resourceVersion: "28617"
    uid: c0c7393b-fce6-46fe-a057-fb2fcbcf62ea
  spec:
    sourcePod: network-check-source-56d84b9f44-xwprz
    targetEndpoint: a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T17:57:48Z"
      message: 'load-balancer-api-internal: tcp connection to a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.346456ms
      message: 'load-balancer-api-internal: tcp connection to a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:03:48Z"
    - latency: 7.343135ms
      message: 'load-balancer-api-internal: resolved host name a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T18:03:48Z"
    - latency: 4.740753ms
      message: 'load-balancer-api-internal: tcp connection to a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:02:48Z"
    - latency: 6.880453ms
      message: 'load-balancer-api-internal: resolved host name a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T18:02:48Z"
    - latency: 3.367546ms
      message: 'load-balancer-api-internal: tcp connection to a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:01:48Z"
    - latency: 8.307669ms
      message: 'load-balancer-api-internal: resolved host name a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T18:01:48Z"
    - latency: 4.892274ms
      message: 'load-balancer-api-internal: tcp connection to a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:00:48Z"
    - latency: 6.720836ms
      message: 'load-balancer-api-internal: resolved host name a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T18:00:48Z"
    - latency: 4.457509ms
      message: 'load-balancer-api-internal: tcp connection to a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:59:48Z"
    - latency: 7.753355ms
      message: 'load-balancer-api-internal: resolved host name a0244f38b3d524c1ba850eb11bda96f9-0ae8db823b9bcc65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T17:59:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T17:51:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-111-to-network-check-target-ip-10-0-128-111
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-111.ec2.internal
      uid: 00cc89b9-c60e-4556-927f-4ec115c5896d
    resourceVersion: "30162"
    uid: 09fc35b0-23e3-47a8-8cbb-8c5090130c3c
  spec:
    sourcePod: network-check-source-56d84b9f44-xwprz
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T17:58:48Z"
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.221181ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:05:48Z"
    - latency: 899.909µs
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:04:48Z"
    - latency: 958.387µs
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:03:48Z"
    - latency: 913.205µs
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:02:48Z"
    - latency: 1.588836ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:01:48Z"
    - latency: 1.428545ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:00:48Z"
    - latency: 1.366159ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:59:48Z"
    - latency: 923.147µs
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:58:48Z"
    - latency: 857.433µs
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:57:48Z"
    - latency: 861.687µs
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:56:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T17:51:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-111-to-network-check-target-ip-10-0-128-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-111.ec2.internal
      uid: 00cc89b9-c60e-4556-927f-4ec115c5896d
    resourceVersion: "30164"
    uid: 4797086d-0125-41fa-b8cb-ec460ec5b525
  spec:
    sourcePod: network-check-source-56d84b9f44-xwprz
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T17:58:48Z"
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.224446ms
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:05:48Z"
    - latency: 2.141837ms
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:04:48Z"
    - latency: 2.242815ms
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:03:48Z"
    - latency: 1.933253ms
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:02:48Z"
    - latency: 2.112111ms
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:01:48Z"
    - latency: 2.327578ms
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:00:48Z"
    - latency: 2.498712ms
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:59:48Z"
    - latency: 2.260327ms
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:58:48Z"
    - latency: 2.024695ms
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:57:48Z"
    - latency: 1.85979ms
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:56:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T17:51:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-111-to-network-check-target-ip-10-0-139-237
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-111.ec2.internal
      uid: 00cc89b9-c60e-4556-927f-4ec115c5896d
    resourceVersion: "30163"
    uid: 7e315d26-5d29-4bf1-a631-dc417107963a
  spec:
    sourcePod: network-check-source-56d84b9f44-xwprz
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T17:58:48Z"
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.907094ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:05:48Z"
    - latency: 1.814545ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:04:48Z"
    - latency: 1.8389ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:03:48Z"
    - latency: 1.916924ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:02:48Z"
    - latency: 1.931543ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:01:48Z"
    - latency: 1.797164ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:00:48Z"
    - latency: 2.068442ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:59:48Z"
    - latency: 1.945299ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:58:48Z"
    - latency: 2.017635ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:57:48Z"
    - latency: 1.925493ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:56:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T17:51:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-111-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-111.ec2.internal
      uid: 00cc89b9-c60e-4556-927f-4ec115c5896d
    resourceVersion: "28615"
    uid: 94feaaeb-0115-475a-a32b-91c9c2d0cdba
  spec:
    sourcePod: network-check-source-56d84b9f44-xwprz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T17:57:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 956.908µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:03:48Z"
    - latency: 1.643719ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T18:03:48Z"
    - latency: 956.617µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:02:48Z"
    - latency: 1.801426ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T18:02:48Z"
    - latency: 869.187µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:01:48Z"
    - latency: 2.319173ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T18:01:48Z"
    - latency: 1.141919ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T18:00:48Z"
    - latency: 1.787001ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T18:00:48Z"
    - latency: 961.08µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T17:59:48Z"
    - latency: 2.455514ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T17:59:48Z"
kind: List
metadata:
  resourceVersion: ""