apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T04:04:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-111-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-111.ec2.internal
      uid: d1da2eff-e5c9-4b38-834d-42a96125619d
    resourceVersion: "54650"
    uid: 68bdafc5-599e-4e09-b218-c3c9c4901556
  spec:
    sourcePod: network-check-source-685456655f-56mr8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T04:11:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 976.823µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:32:54Z"
    - latency: 1.413098ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:31:54Z"
    - latency: 859.309µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:30:54Z"
    - latency: 860.933µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:29:54Z"
    - latency: 935.31µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:28:54Z"
    - latency: 903.25µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:27:54Z"
    - latency: 1.199048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:26:54Z"
    - latency: 1.200132ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:25:54Z"
    - latency: 1.107985ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:24:54Z"
    - latency: 818.291µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:23:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T04:04:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-111-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-111.ec2.internal
      uid: d1da2eff-e5c9-4b38-834d-42a96125619d
    resourceVersion: "56033"
    uid: a6541409-19d2-41d0-9e4c-f013757c727d
  spec:
    sourcePod: network-check-source-685456655f-56mr8
    targetEndpoint: a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T04:10:54Z"
      message: 'load-balancer-api-external: tcp connection to a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.326852ms
      message: 'load-balancer-api-external: tcp connection to a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:34:54Z"
    - latency: 7.744932ms
      message: 'load-balancer-api-external: resolved host name a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:34:54Z"
    - latency: 5.863322ms
      message: 'load-balancer-api-external: tcp connection to a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:33:54Z"
    - latency: 8.116116ms
      message: 'load-balancer-api-external: resolved host name a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:33:54Z"
    - latency: 5.566314ms
      message: 'load-balancer-api-external: tcp connection to a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:32:54Z"
    - latency: 6.368189ms
      message: 'load-balancer-api-external: resolved host name a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:32:54Z"
    - latency: 4.03038ms
      message: 'load-balancer-api-external: tcp connection to a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:31:54Z"
    - latency: 8.342851ms
      message: 'load-balancer-api-external: resolved host name a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:31:54Z"
    - latency: 4.26715ms
      message: 'load-balancer-api-external: tcp connection to a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:30:54Z"
    - latency: 7.854194ms
      message: 'load-balancer-api-external: resolved host name a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:30:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T04:04:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-111-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-111.ec2.internal
      uid: d1da2eff-e5c9-4b38-834d-42a96125619d
    resourceVersion: "56032"
    uid: 5070b038-8955-47d0-917a-57efb4f2720f
  spec:
    sourcePod: network-check-source-685456655f-56mr8
    targetEndpoint: a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T04:10:54Z"
      message: 'load-balancer-api-internal: tcp connection to a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.559063ms
      message: 'load-balancer-api-internal: tcp connection to a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:34:54Z"
    - latency: 7.784074ms
      message: 'load-balancer-api-internal: resolved host name a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:34:54Z"
    - latency: 4.608914ms
      message: 'load-balancer-api-internal: tcp connection to a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:33:54Z"
    - latency: 8.16583ms
      message: 'load-balancer-api-internal: resolved host name a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:33:54Z"
    - latency: 5.578217ms
      message: 'load-balancer-api-internal: tcp connection to a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:32:54Z"
    - latency: 6.463656ms
      message: 'load-balancer-api-internal: resolved host name a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:32:54Z"
    - latency: 4.834403ms
      message: 'load-balancer-api-internal: tcp connection to a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:31:54Z"
    - latency: 8.21615ms
      message: 'load-balancer-api-internal: resolved host name a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:31:54Z"
    - latency: 4.273859ms
      message: 'load-balancer-api-internal: tcp connection to a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:30:54Z"
    - latency: 7.893584ms
      message: 'load-balancer-api-internal: resolved host name a8bfa561e7a3943a79cc5d5bbf93ef8a-3814e739d25a4fc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:30:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T04:04:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-111-to-network-check-target-ip-10-0-130-111
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-111.ec2.internal
      uid: d1da2eff-e5c9-4b38-834d-42a96125619d
    resourceVersion: "54647"
    uid: 71946c3d-c2a4-4cb9-bbfa-4d88ab552d44
  spec:
    sourcePod: network-check-source-685456655f-56mr8
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T04:11:54Z"
      message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.198006ms
      message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:32:54Z"
    - latency: 1.656797ms
      message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:31:54Z"
    - latency: 1.481415ms
      message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:30:54Z"
    - latency: 1.162138ms
      message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:29:54Z"
    - latency: 850.179µs
      message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:28:54Z"
    - latency: 926.099µs
      message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:27:54Z"
    - latency: 1.147943ms
      message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:26:54Z"
    - latency: 863.952µs
      message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:25:54Z"
    - latency: 969.857µs
      message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:24:54Z"
    - latency: 1.261009ms
      message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:23:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T04:04:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-111-to-network-check-target-ip-10-0-133-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-111.ec2.internal
      uid: d1da2eff-e5c9-4b38-834d-42a96125619d
    resourceVersion: "54648"
    uid: ed6e4e97-4be0-4de0-ab2d-c7b701bcceb0
  spec:
    sourcePod: network-check-source-685456655f-56mr8
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T04:11:54Z"
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.312195ms
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:32:54Z"
    - latency: 2.4398ms
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:31:54Z"
    - latency: 2.776762ms
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:30:54Z"
    - latency: 2.280454ms
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:29:54Z"
    - latency: 2.423345ms
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:28:54Z"
    - latency: 2.425272ms
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:27:54Z"
    - latency: 2.234439ms
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:26:54Z"
    - latency: 2.21208ms
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:25:54Z"
    - latency: 2.813163ms
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:24:54Z"
    - latency: 2.521854ms
      message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:23:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T04:04:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-111-to-network-check-target-ip-10-0-143-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-111.ec2.internal
      uid: d1da2eff-e5c9-4b38-834d-42a96125619d
    resourceVersion: "54649"
    uid: 7a9555c3-e51e-43a6-9607-2323c12b5485
  spec:
    sourcePod: network-check-source-685456655f-56mr8
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T04:11:54Z"
      message: 'network-check-target-ip-10-0-143-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.681414ms
      message: 'network-check-target-ip-10-0-143-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:32:54Z"
    - latency: 2.408239ms
      message: 'network-check-target-ip-10-0-143-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:31:54Z"
    - latency: 1.883552ms
      message: 'network-check-target-ip-10-0-143-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:30:54Z"
    - latency: 2.244431ms
      message: 'network-check-target-ip-10-0-143-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:29:54Z"
    - latency: 2.478228ms
      message: 'network-check-target-ip-10-0-143-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:28:54Z"
    - latency: 2.49714ms
      message: 'network-check-target-ip-10-0-143-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:27:54Z"
    - latency: 2.110331ms
      message: 'network-check-target-ip-10-0-143-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:26:54Z"
    - latency: 2.165122ms
      message: 'network-check-target-ip-10-0-143-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:25:54Z"
    - latency: 2.27666ms
      message: 'network-check-target-ip-10-0-143-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:24:54Z"
    - latency: 2.325625ms
      message: 'network-check-target-ip-10-0-143-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:23:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T04:04:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-111-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-111.ec2.internal
      uid: d1da2eff-e5c9-4b38-834d-42a96125619d
    resourceVersion: "56031"
    uid: 6aafcb92-371f-45ee-a1a4-451f5ad2d91b
  spec:
    sourcePod: network-check-source-685456655f-56mr8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T04:10:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 826.388µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:34:54Z"
    - latency: 1.665675ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:34:54Z"
    - latency: 1.198197ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:33:54Z"
    - latency: 1.924651ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:33:54Z"
    - latency: 889.157µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:32:54Z"
    - latency: 1.6749ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:32:54Z"
    - latency: 945.029µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:31:54Z"
    - latency: 1.743381ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:31:54Z"
    - latency: 947.339µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:30:54Z"
    - latency: 1.932785ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:30:54Z"
kind: List
metadata:
  resourceVersion: ""