apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T14:18:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-65-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-65.ec2.internal
      uid: d1e746f8-cea2-4a39-be9f-0d3def86a3c8
    resourceVersion: "31198"
    uid: b6263c75-c3b7-433d-8e66-3c0edbac9573
  spec:
    sourcePod: network-check-source-8894fc9bd-lqv79
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T14:26:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.030869ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:01:00Z"
    - latency: 842.97µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:00:00Z"
    - latency: 999.816µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:59:00Z"
    - latency: 952.071µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:58:00Z"
    - latency: 1.089293ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:57:00Z"
    - latency: 870.342µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:56:00Z"
    - latency: 977.847µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:55:00Z"
    - latency: 1.041966ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:54:00Z"
    - latency: 843.086µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:53:00Z"
    - latency: 1.274104ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:52:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T14:18:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-65-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-65.ec2.internal
      uid: d1e746f8-cea2-4a39-be9f-0d3def86a3c8
    resourceVersion: "31199"
    uid: 7b00a5f8-6c19-4f27-893f-888210f6f71f
  spec:
    sourcePod: network-check-source-8894fc9bd-lqv79
    targetEndpoint: acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T14:25:00Z"
      message: 'load-balancer-api-external: tcp connection to acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.648349ms
      message: 'load-balancer-api-external: tcp connection to acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:01:00Z"
    - latency: 8.710139ms
      message: 'load-balancer-api-external: resolved host name acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:01:00Z"
    - latency: 5.343638ms
      message: 'load-balancer-api-external: tcp connection to acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:00:00Z"
    - latency: 10.049669ms
      message: 'load-balancer-api-external: resolved host name acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:00:00Z"
    - latency: 3.57921ms
      message: 'load-balancer-api-external: tcp connection to acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:59:00Z"
    - latency: 11.072217ms
      message: 'load-balancer-api-external: resolved host name acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T14:59:00Z"
    - latency: 4.972656ms
      message: 'load-balancer-api-external: tcp connection to acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:58:00Z"
    - latency: 9.544063ms
      message: 'load-balancer-api-external: resolved host name acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T14:58:00Z"
    - latency: 5.289157ms
      message: 'load-balancer-api-external: tcp connection to acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:57:00Z"
    - latency: 11.876934ms
      message: 'load-balancer-api-external: resolved host name acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T14:57:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T14:18:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-65-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-65.ec2.internal
      uid: d1e746f8-cea2-4a39-be9f-0d3def86a3c8
    resourceVersion: "31200"
    uid: f3bfba39-cdfe-4d3f-90aa-ab8e2eedbc05
  spec:
    sourcePod: network-check-source-8894fc9bd-lqv79
    targetEndpoint: acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T14:25:00Z"
      message: 'load-balancer-api-internal: tcp connection to acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.651475ms
      message: 'load-balancer-api-internal: tcp connection to acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:01:00Z"
    - latency: 8.743884ms
      message: 'load-balancer-api-internal: resolved host name acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:01:00Z"
    - latency: 3.562306ms
      message: 'load-balancer-api-internal: tcp connection to acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:00:00Z"
    - latency: 10.087535ms
      message: 'load-balancer-api-internal: resolved host name acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:00:00Z"
    - latency: 5.043251ms
      message: 'load-balancer-api-internal: tcp connection to acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:59:00Z"
    - latency: 11.094639ms
      message: 'load-balancer-api-internal: resolved host name acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T14:59:00Z"
    - latency: 4.959706ms
      message: 'load-balancer-api-internal: tcp connection to acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:58:00Z"
    - latency: 9.5694ms
      message: 'load-balancer-api-internal: resolved host name acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T14:58:00Z"
    - latency: 5.361388ms
      message: 'load-balancer-api-internal: tcp connection to acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:57:00Z"
    - latency: 11.981031ms
      message: 'load-balancer-api-internal: resolved host name acdb166417a3143c6baed2f381c11d1a-49409844364ddaea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T14:57:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T14:18:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-65-to-network-check-target-ip-10-0-130-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-65.ec2.internal
      uid: d1e746f8-cea2-4a39-be9f-0d3def86a3c8
    resourceVersion: "31196"
    uid: 9ff85881-b562-4056-a9ba-83401546b278
  spec:
    sourcePod: network-check-source-8894fc9bd-lqv79
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T14:26:00Z"
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.302739ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:01:00Z"
    - latency: 2.142705ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:00:00Z"
    - latency: 2.209631ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:59:00Z"
    - latency: 2.150153ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:58:00Z"
    - latency: 2.336052ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:57:00Z"
    - latency: 2.348652ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:56:00Z"
    - latency: 2.170594ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:55:00Z"
    - latency: 2.284126ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:54:00Z"
    - latency: 2.559261ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:53:00Z"
    - latency: 2.261966ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:52:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T14:18:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-65-to-network-check-target-ip-10-0-133-65
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-65.ec2.internal
      uid: d1e746f8-cea2-4a39-be9f-0d3def86a3c8
    resourceVersion: "31194"
    uid: 660cf4fd-b4f4-4be0-a4a3-a755ed9fb186
  spec:
    sourcePod: network-check-source-8894fc9bd-lqv79
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T14:26:00Z"
      message: 'network-check-target-ip-10-0-133-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 919.57µs
      message: 'network-check-target-ip-10-0-133-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:01:00Z"
    - latency: 936.388µs
      message: 'network-check-target-ip-10-0-133-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:00:00Z"
    - latency: 833.785µs
      message: 'network-check-target-ip-10-0-133-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:59:00Z"
    - latency: 849.724µs
      message: 'network-check-target-ip-10-0-133-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:58:00Z"
    - latency: 966.804µs
      message: 'network-check-target-ip-10-0-133-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:57:00Z"
    - latency: 759.561µs
      message: 'network-check-target-ip-10-0-133-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:56:00Z"
    - latency: 1.389307ms
      message: 'network-check-target-ip-10-0-133-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:55:00Z"
    - latency: 835.297µs
      message: 'network-check-target-ip-10-0-133-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:54:00Z"
    - latency: 1.318461ms
      message: 'network-check-target-ip-10-0-133-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:53:00Z"
    - latency: 815.623µs
      message: 'network-check-target-ip-10-0-133-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:52:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T14:18:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-65-to-network-check-target-ip-10-0-137-106
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-65.ec2.internal
      uid: d1e746f8-cea2-4a39-be9f-0d3def86a3c8
    resourceVersion: "31195"
    uid: c50703dd-45d2-4526-90a8-bdebf3dd8b12
  spec:
    sourcePod: network-check-source-8894fc9bd-lqv79
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T14:26:00Z"
      message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.891631ms
      message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:01:00Z"
    - latency: 1.924811ms
      message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:00:00Z"
    - latency: 2.30458ms
      message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:59:00Z"
    - latency: 1.934434ms
      message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:58:00Z"
    - latency: 2.221856ms
      message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:57:00Z"
    - latency: 2.043619ms
      message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:56:00Z"
    - latency: 2.101626ms
      message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:55:00Z"
    - latency: 2.136747ms
      message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:54:00Z"
    - latency: 2.046512ms
      message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:53:00Z"
    - latency: 1.776437ms
      message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:52:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T14:18:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-65-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-65.ec2.internal
      uid: d1e746f8-cea2-4a39-be9f-0d3def86a3c8
    resourceVersion: "31197"
    uid: ecd6ee51-6e16-40eb-9e77-6212cbfbc427
  spec:
    sourcePod: network-check-source-8894fc9bd-lqv79
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T14:25:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 829.904µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:01:00Z"
    - latency: 1.560203ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:01:00Z"
    - latency: 1.050746ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:00:00Z"
    - latency: 1.656799ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:00:00Z"
    - latency: 860.193µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:59:00Z"
    - latency: 1.625297ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T14:59:00Z"
    - latency: 900.165µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:58:00Z"
    - latency: 2.068027ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T14:58:00Z"
    - latency: 959.689µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T14:57:00Z"
    - latency: 1.754759ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T14:57:00Z"
kind: List
metadata:
  resourceVersion: ""