apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-19T15:28:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-48-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-48.ec2.internal
      uid: 7944eb3e-1853-402e-a4e4-7ffb52133ae6
    resourceVersion: "43826"
    uid: dadc8a89-5191-49a4-8db3-339424eecf89
  spec:
    sourcePod: network-check-source-8894fc9bd-f7z6w
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-19T15:35:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.004836ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:56:10Z"
    - latency: 1.037362ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:55:10Z"
    - latency: 1.006554ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:54:10Z"
    - latency: 1.023783ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:53:10Z"
    - latency: 820.725µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:52:10Z"
    - latency: 1.177097ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:51:10Z"
    - latency: 1.500837ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:50:10Z"
    - latency: 1.052797ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:49:10Z"
    - latency: 1.132183ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:48:10Z"
    - latency: 1.077273ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:47:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-19T15:28:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-48-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-48.ec2.internal
      uid: 7944eb3e-1853-402e-a4e4-7ffb52133ae6
    resourceVersion: "46087"
    uid: 3c55c00d-6ea7-4199-a93b-a6345544f297
  spec:
    sourcePod: network-check-source-8894fc9bd-f7z6w
    targetEndpoint: ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-19T15:34:10Z"
      message: 'load-balancer-api-external: tcp connection to ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.802182ms
      message: 'load-balancer-api-external: tcp connection to ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:58:10Z"
    - latency: 8.363606ms
      message: 'load-balancer-api-external: resolved host name ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T15:58:10Z"
    - latency: 4.983655ms
      message: 'load-balancer-api-external: tcp connection to ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:57:10Z"
    - latency: 21.358786ms
      message: 'load-balancer-api-external: resolved host name ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T15:57:10Z"
    - latency: 3.172704ms
      message: 'load-balancer-api-external: tcp connection to ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:56:10Z"
    - latency: 8.123612ms
      message: 'load-balancer-api-external: resolved host name ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T15:56:10Z"
    - latency: 4.716228ms
      message: 'load-balancer-api-external: tcp connection to ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:55:10Z"
    - latency: 8.175655ms
      message: 'load-balancer-api-external: resolved host name ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T15:55:10Z"
    - latency: 3.795849ms
      message: 'load-balancer-api-external: tcp connection to ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:54:10Z"
    - latency: 7.872994ms
      message: 'load-balancer-api-external: resolved host name ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T15:54:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-19T15:28:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-48-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-48.ec2.internal
      uid: 7944eb3e-1853-402e-a4e4-7ffb52133ae6
    resourceVersion: "46086"
    uid: c7525cbc-e00d-4a36-9913-61d73e95362a
  spec:
    sourcePod: network-check-source-8894fc9bd-f7z6w
    targetEndpoint: ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-19T15:34:10Z"
      message: 'load-balancer-api-internal: tcp connection to ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.846491ms
      message: 'load-balancer-api-internal: tcp connection to ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:58:10Z"
    - latency: 8.334721ms
      message: 'load-balancer-api-internal: resolved host name ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T15:58:10Z"
    - latency: 3.382908ms
      message: 'load-balancer-api-internal: tcp connection to ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:57:10Z"
    - latency: 21.236663ms
      message: 'load-balancer-api-internal: resolved host name ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T15:57:10Z"
    - latency: 4.396959ms
      message: 'load-balancer-api-internal: tcp connection to ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:56:10Z"
    - latency: 8.073926ms
      message: 'load-balancer-api-internal: resolved host name ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T15:56:10Z"
    - latency: 4.727364ms
      message: 'load-balancer-api-internal: tcp connection to ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:55:10Z"
    - latency: 7.996241ms
      message: 'load-balancer-api-internal: resolved host name ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T15:55:10Z"
    - latency: 3.783456ms
      message: 'load-balancer-api-internal: tcp connection to ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:54:10Z"
    - latency: 7.820794ms
      message: 'load-balancer-api-internal: resolved host name ae20157355de544c597d8b7c8027283f-5dc4776cc2bfd4a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T15:54:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-19T15:28:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-48-to-network-check-target-ip-10-0-130-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-48.ec2.internal
      uid: 7944eb3e-1853-402e-a4e4-7ffb52133ae6
    resourceVersion: "43824"
    uid: 73a77937-d3cf-422e-9d82-9ba487c9a5f9
  spec:
    sourcePod: network-check-source-8894fc9bd-f7z6w
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-19T15:35:10Z"
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.948175ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:56:10Z"
    - latency: 1.881876ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:55:10Z"
    - latency: 1.797307ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:54:10Z"
    - latency: 1.96976ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:53:10Z"
    - latency: 2.057292ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:52:10Z"
    - latency: 1.857203ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:51:10Z"
    - latency: 1.965622ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:50:10Z"
    - latency: 1.889417ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:49:10Z"
    - latency: 2.003974ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:48:10Z"
    - latency: 1.990568ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:47:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-19T15:28:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-48-to-network-check-target-ip-10-0-131-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-48.ec2.internal
      uid: 7944eb3e-1853-402e-a4e4-7ffb52133ae6
    resourceVersion: "43823"
    uid: 97dae3b3-bc2a-4596-8edb-c26311f287fb
  spec:
    sourcePod: network-check-source-8894fc9bd-f7z6w
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-19T15:35:10Z"
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 794.368µs
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:56:10Z"
    - latency: 857.232µs
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:55:10Z"
    - latency: 876.515µs
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:54:10Z"
    - latency: 748.603µs
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:53:10Z"
    - latency: 462.191µs
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:52:10Z"
    - latency: 1.115147ms
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:51:10Z"
    - latency: 800.982µs
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:50:10Z"
    - latency: 764.734µs
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:49:10Z"
    - latency: 816.248µs
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:48:10Z"
    - latency: 995.126µs
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:47:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-19T15:28:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-48-to-network-check-target-ip-10-0-133-218
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-48.ec2.internal
      uid: 7944eb3e-1853-402e-a4e4-7ffb52133ae6
    resourceVersion: "43825"
    uid: ac0590dc-535c-46ae-aeb6-21a8346473d7
  spec:
    sourcePod: network-check-source-8894fc9bd-f7z6w
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-19T15:35:10Z"
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.460593ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:56:10Z"
    - latency: 2.213628ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:55:10Z"
    - latency: 2.115271ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:54:10Z"
    - latency: 1.893706ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:53:10Z"
    - latency: 2.097349ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:52:10Z"
    - latency: 2.194062ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:51:10Z"
    - latency: 2.020433ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:50:10Z"
    - latency: 2.362446ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:49:10Z"
    - latency: 2.0312ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:48:10Z"
    - latency: 2.282077ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:47:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-19T15:28:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-48-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-48.ec2.internal
      uid: 7944eb3e-1853-402e-a4e4-7ffb52133ae6
    resourceVersion: "46084"
    uid: d7d8082c-6593-4b60-9029-6ad628c02cbb
  spec:
    sourcePod: network-check-source-8894fc9bd-f7z6w
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-19T15:34:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.018µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:58:10Z"
    - latency: 2.152048ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T15:58:10Z"
    - latency: 767.869µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:57:10Z"
    - latency: 1.926323ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T15:57:10Z"
    - latency: 784.012µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:56:10Z"
    - latency: 1.616359ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T15:56:10Z"
    - latency: 864.103µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:55:10Z"
    - latency: 1.759466ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T15:55:10Z"
    - latency: 840.494µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T15:54:10Z"
    - latency: 1.695423ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T15:54:10Z"
kind: List
metadata:
  resourceVersion: ""