apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T07:08:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-164-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-164.ec2.internal
      uid: 5d0c6993-f189-4180-bf3a-0280f3b42cc4
    resourceVersion: "54246"
    uid: e0de1963-500b-47e7-aa70-f0d1bb7fe2b2
  spec:
    sourcePod: network-check-source-685456655f-nxclz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T07:15:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 844.012µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:36:35Z"
    - latency: 884.613µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:35:35Z"
    - latency: 963.575µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:34:35Z"
    - latency: 972.332µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:33:35Z"
    - latency: 965.098µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:32:35Z"
    - latency: 7.141866ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:31:35Z"
    - latency: 1.090081ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:30:35Z"
    - latency: 1.153693ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:29:35Z"
    - latency: 1.098458ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:28:35Z"
    - latency: 1.16638ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:27:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T07:08:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-164-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-164.ec2.internal
      uid: 5d0c6993-f189-4180-bf3a-0280f3b42cc4
    resourceVersion: "55817"
    uid: b120430d-00b9-4e50-a5dc-78c901cf240d
  spec:
    sourcePod: network-check-source-685456655f-nxclz
    targetEndpoint: a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T07:14:35Z"
      message: 'load-balancer-api-external: tcp connection to a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.737584ms
      message: 'load-balancer-api-external: tcp connection to a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:38:35Z"
    - latency: 8.839352ms
      message: 'load-balancer-api-external: resolved host name a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T07:38:35Z"
    - latency: 5.266288ms
      message: 'load-balancer-api-external: tcp connection to a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:37:35Z"
    - latency: 9.386529ms
      message: 'load-balancer-api-external: resolved host name a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T07:37:35Z"
    - latency: 6.24033ms
      message: 'load-balancer-api-external: tcp connection to a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:36:35Z"
    - latency: 9.459217ms
      message: 'load-balancer-api-external: resolved host name a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T07:36:35Z"
    - latency: 5.10492ms
      message: 'load-balancer-api-external: tcp connection to a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:35:35Z"
    - latency: 9.240135ms
      message: 'load-balancer-api-external: resolved host name a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T07:35:35Z"
    - latency: 3.79364ms
      message: 'load-balancer-api-external: tcp connection to a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:34:35Z"
    - latency: 9.083656ms
      message: 'load-balancer-api-external: resolved host name a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T07:34:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T07:08:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-164-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-164.ec2.internal
      uid: 5d0c6993-f189-4180-bf3a-0280f3b42cc4
    resourceVersion: "55818"
    uid: 43288a33-4095-4f45-9bd1-d92aeb8a31d9
  spec:
    sourcePod: network-check-source-685456655f-nxclz
    targetEndpoint: a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T07:14:35Z"
      message: 'load-balancer-api-internal: tcp connection to a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.742268ms
      message: 'load-balancer-api-internal: tcp connection to a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:38:35Z"
    - latency: 8.734028ms
      message: 'load-balancer-api-internal: resolved host name a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T07:38:35Z"
    - latency: 4.281671ms
      message: 'load-balancer-api-internal: tcp connection to a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:37:35Z"
    - latency: 9.311638ms
      message: 'load-balancer-api-internal: resolved host name a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T07:37:35Z"
    - latency: 5.346837ms
      message: 'load-balancer-api-internal: tcp connection to a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:36:35Z"
    - latency: 9.283658ms
      message: 'load-balancer-api-internal: resolved host name a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T07:36:35Z"
    - latency: 5.095236ms
      message: 'load-balancer-api-internal: tcp connection to a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:35:35Z"
    - latency: 9.168119ms
      message: 'load-balancer-api-internal: resolved host name a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T07:35:35Z"
    - latency: 4.041029ms
      message: 'load-balancer-api-internal: tcp connection to a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:34:35Z"
    - latency: 9.006643ms
      message: 'load-balancer-api-internal: resolved host name a5d59e56370b94c39a9426c97cb9daad-a4e4425ed0f545f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T07:34:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T07:08:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-164-to-network-check-target-ip-10-0-133-164
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-164.ec2.internal
      uid: 5d0c6993-f189-4180-bf3a-0280f3b42cc4
    resourceVersion: "54243"
    uid: 032dac3b-a701-4eb1-a529-c684fcf17419
  spec:
    sourcePod: network-check-source-685456655f-nxclz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T07:15:35Z"
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 982.727µs
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:36:35Z"
    - latency: 911.743µs
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:35:35Z"
    - latency: 594.434µs
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:34:35Z"
    - latency: 772.848µs
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:33:35Z"
    - latency: 1.358759ms
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:32:35Z"
    - latency: 7.362518ms
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:31:35Z"
    - latency: 704.347µs
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:30:35Z"
    - latency: 1.249607ms
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:29:35Z"
    - latency: 1.072164ms
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:28:35Z"
    - latency: 1.457617ms
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:27:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T07:08:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-164-to-network-check-target-ip-10-0-139-109
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-164.ec2.internal
      uid: 5d0c6993-f189-4180-bf3a-0280f3b42cc4
    resourceVersion: "54245"
    uid: 7661626b-9acd-481b-9ff8-588456f451bf
  spec:
    sourcePod: network-check-source-685456655f-nxclz
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T07:15:35Z"
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.250435ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:36:35Z"
    - latency: 2.44045ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:35:35Z"
    - latency: 2.366612ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:34:35Z"
    - latency: 2.213765ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:33:35Z"
    - latency: 2.56136ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:32:35Z"
    - latency: 6.391987ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:31:35Z"
    - latency: 2.440572ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:30:35Z"
    - latency: 2.497081ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:29:35Z"
    - latency: 2.652674ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:28:35Z"
    - latency: 2.952666ms
      message: 'network-check-target-ip-10-0-139-109: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:27:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T07:08:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-164-to-network-check-target-ip-10-0-142-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-164.ec2.internal
      uid: 5d0c6993-f189-4180-bf3a-0280f3b42cc4
    resourceVersion: "54244"
    uid: eed3457e-7a83-40db-b428-6ecf25a20978
  spec:
    sourcePod: network-check-source-685456655f-nxclz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T07:15:35Z"
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.275134ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:36:35Z"
    - latency: 2.610635ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:35:35Z"
    - latency: 2.174108ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:34:35Z"
    - latency: 2.135414ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:33:35Z"
    - latency: 2.345862ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:32:35Z"
    - latency: 6.537018ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:31:35Z"
    - latency: 2.038068ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:30:35Z"
    - latency: 2.463803ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:29:35Z"
    - latency: 2.619599ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:28:35Z"
    - latency: 2.331317ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:27:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T07:08:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-164-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-164.ec2.internal
      uid: 5d0c6993-f189-4180-bf3a-0280f3b42cc4
    resourceVersion: "55816"
    uid: 88e167b0-0eb3-4b75-9a5e-c10f33b56b3e
  spec:
    sourcePod: network-check-source-685456655f-nxclz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T07:14:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 917.078µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:38:35Z"
    - latency: 1.579956ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T07:38:35Z"
    - latency: 829.939µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:37:35Z"
    - latency: 2.187293ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T07:37:35Z"
    - latency: 1.388036ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:36:35Z"
    - latency: 1.851775ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T07:36:35Z"
    - latency: 910.329µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:35:35Z"
    - latency: 2.5068ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T07:35:35Z"
    - latency: 845.995µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T07:34:35Z"
    - latency: 1.380661ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T07:34:35Z"
kind: List
metadata:
  resourceVersion: ""