apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:07:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-233-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-233.ec2.internal
      uid: 9bf87550-acb8-4417-a208-c72aeb2661c1
    resourceVersion: "21508"
    uid: 4e775c99-0982-4f62-8ee4-3fd6433c5fd3
  spec:
    sourcePod: network-check-source-869dcfcdcd-dcnnv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:14:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 973.124µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:28:27Z"
    - latency: 933.581µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:27:27Z"
    - latency: 799.284µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:26:27Z"
    - latency: 870.549µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:25:27Z"
    - latency: 1.196732ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:24:27Z"
    - latency: 1.065479ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:23:27Z"
    - latency: 821.802µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:22:27Z"
    - latency: 777.754µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:21:27Z"
    - latency: 927.585µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:20:27Z"
    - latency: 877.716µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:19:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:07:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-233-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-233.ec2.internal
      uid: 9bf87550-acb8-4417-a208-c72aeb2661c1
    resourceVersion: "20182"
    uid: 5ee0b53c-9391-4d1a-8cea-5847e171de49
  spec:
    sourcePod: network-check-source-869dcfcdcd-dcnnv
    targetEndpoint: aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:13:27Z"
      message: 'load-balancer-api-external: tcp connection to aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.591371ms
      message: 'load-balancer-api-external: tcp connection to aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:25:27Z"
    - latency: 6.151658ms
      message: 'load-balancer-api-external: resolved host name aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:25:27Z"
    - latency: 5.309914ms
      message: 'load-balancer-api-external: tcp connection to aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:24:27Z"
    - latency: 6.695538ms
      message: 'load-balancer-api-external: resolved host name aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:24:27Z"
    - latency: 6.887381ms
      message: 'load-balancer-api-external: tcp connection to aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:23:27Z"
    - latency: 6.339783ms
      message: 'load-balancer-api-external: resolved host name aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:23:27Z"
    - latency: 4.271062ms
      message: 'load-balancer-api-external: tcp connection to aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:22:27Z"
    - latency: 6.439799ms
      message: 'load-balancer-api-external: resolved host name aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:22:27Z"
    - latency: 6.958041ms
      message: 'load-balancer-api-external: tcp connection to aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:21:27Z"
    - latency: 8.402791ms
      message: 'load-balancer-api-external: resolved host name aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:21:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:07:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-233-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-233.ec2.internal
      uid: 9bf87550-acb8-4417-a208-c72aeb2661c1
    resourceVersion: "20181"
    uid: 9d6a1fe3-5fa4-4973-abf4-10557de8dadc
  spec:
    sourcePod: network-check-source-869dcfcdcd-dcnnv
    targetEndpoint: aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:13:27Z"
      message: 'load-balancer-api-internal: tcp connection to aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.292922ms
      message: 'load-balancer-api-internal: tcp connection to aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:25:27Z"
    - latency: 6.225348ms
      message: 'load-balancer-api-internal: resolved host name aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:25:27Z"
    - latency: 5.26673ms
      message: 'load-balancer-api-internal: tcp connection to aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:24:27Z"
    - latency: 6.777887ms
      message: 'load-balancer-api-internal: resolved host name aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:24:27Z"
    - latency: 5.210901ms
      message: 'load-balancer-api-internal: tcp connection to aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:23:27Z"
    - latency: 6.465795ms
      message: 'load-balancer-api-internal: resolved host name aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:23:27Z"
    - latency: 6.082477ms
      message: 'load-balancer-api-internal: tcp connection to aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:22:27Z"
    - latency: 5.474779ms
      message: 'load-balancer-api-internal: resolved host name aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:22:27Z"
    - latency: 5.559681ms
      message: 'load-balancer-api-internal: tcp connection to aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:21:27Z"
    - latency: 8.514947ms
      message: 'load-balancer-api-internal: resolved host name aad88a07a748147c592c7eacff66e11a-d2d95c59a702f474.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:21:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:07:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-233-to-network-check-target-ip-10-0-135-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-233.ec2.internal
      uid: 9bf87550-acb8-4417-a208-c72aeb2661c1
    resourceVersion: "21507"
    uid: 94bffd07-e8a9-4efa-8aca-c44a32e6e2ff
  spec:
    sourcePod: network-check-source-869dcfcdcd-dcnnv
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:14:27Z"
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.097348ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:28:27Z"
    - latency: 2.3101ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:27:27Z"
    - latency: 2.221584ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:26:27Z"
    - latency: 2.351806ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:25:27Z"
    - latency: 2.639884ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:24:27Z"
    - latency: 2.239805ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:23:27Z"
    - latency: 2.02351ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:22:27Z"
    - latency: 2.434893ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:21:27Z"
    - latency: 2.335344ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:20:27Z"
    - latency: 2.162503ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:19:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:07:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-233-to-network-check-target-ip-10-0-137-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-233.ec2.internal
      uid: 9bf87550-acb8-4417-a208-c72aeb2661c1
    resourceVersion: "21505"
    uid: 180c88a0-4a8c-4133-8739-8e138ff62eb8
  spec:
    sourcePod: network-check-source-869dcfcdcd-dcnnv
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:14:27Z"
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.05131ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:28:27Z"
    - latency: 801.138µs
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:27:27Z"
    - latency: 1.148398ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:26:27Z"
    - latency: 761.274µs
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:25:27Z"
    - latency: 1.4693ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:24:27Z"
    - latency: 800.949µs
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:23:27Z"
    - latency: 1.020131ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:22:27Z"
    - latency: 917.428µs
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:21:27Z"
    - latency: 1.034882ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:20:27Z"
    - latency: 1.145258ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:19:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:07:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-233-to-network-check-target-ip-10-0-142-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-233.ec2.internal
      uid: 9bf87550-acb8-4417-a208-c72aeb2661c1
    resourceVersion: "21506"
    uid: 87302cca-a407-43c3-98d6-2fb62923e41c
  spec:
    sourcePod: network-check-source-869dcfcdcd-dcnnv
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:14:27Z"
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.118594ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:28:27Z"
    - latency: 2.223301ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:27:27Z"
    - latency: 2.066823ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:26:27Z"
    - latency: 2.237704ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:25:27Z"
    - latency: 2.326201ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:24:27Z"
    - latency: 2.220455ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:23:27Z"
    - latency: 2.333782ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:22:27Z"
    - latency: 7.634519ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:21:27Z"
    - latency: 2.258824ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:20:27Z"
    - latency: 2.017598ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:19:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:07:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-233-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-233.ec2.internal
      uid: 9bf87550-acb8-4417-a208-c72aeb2661c1
    resourceVersion: "20180"
    uid: f3fd3146-988b-43dc-9626-0d29d7eb3ec7
  spec:
    sourcePod: network-check-source-869dcfcdcd-dcnnv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:13:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 881.588µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:25:27Z"
    - latency: 1.456683ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:25:27Z"
    - latency: 1.43402ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:24:27Z"
    - latency: 1.718756ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:24:27Z"
    - latency: 1.216431ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:23:27Z"
    - latency: 1.731413ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:23:27Z"
    - latency: 913.153µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:22:27Z"
    - latency: 1.607328ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:22:27Z"
    - latency: 850.64µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:21:27Z"
    - latency: 2.073907ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:21:27Z"
kind: List
metadata:
  resourceVersion: ""