apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:30:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-164-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-164.ec2.internal
      uid: 762c99b6-1ad4-48a0-a1d2-ffeed14ea630
    resourceVersion: "85902"
    uid: a7889cda-6b8f-4ef4-b946-3e708a5ec5e4
  spec:
    sourcePod: network-check-source-6f8b768455-vcdhl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:37:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.585683ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:40:38Z"
    - latency: 1.062532ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:39:38Z"
    - latency: 932.794µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:38:38Z"
    - latency: 994.779µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:37:38Z"
    - latency: 1.177079ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:36:38Z"
    - latency: 1.045488ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:35:38Z"
    - latency: 913.524µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:34:38Z"
    - latency: 1.204046ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:33:38Z"
    - latency: 1.050505ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:32:38Z"
    - latency: 877.308µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:31:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:30:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-164-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-164.ec2.internal
      uid: 762c99b6-1ad4-48a0-a1d2-ffeed14ea630
    resourceVersion: "87860"
    uid: 12cf770a-9718-4e61-986e-5dac8ff43850
  spec:
    sourcePod: network-check-source-6f8b768455-vcdhl
    targetEndpoint: ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:36:38Z"
      message: 'load-balancer-api-external: tcp connection to ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.000655ms
      message: 'load-balancer-api-external: tcp connection to ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:42:38Z"
    - latency: 8.553618ms
      message: 'load-balancer-api-external: resolved host name ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:42:38Z"
    - latency: 4.320143ms
      message: 'load-balancer-api-external: tcp connection to ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:41:38Z"
    - latency: 9.005477ms
      message: 'load-balancer-api-external: resolved host name ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:41:38Z"
    - latency: 6.397417ms
      message: 'load-balancer-api-external: tcp connection to ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:40:38Z"
    - latency: 10.792711ms
      message: 'load-balancer-api-external: resolved host name ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:40:38Z"
    - latency: 5.108853ms
      message: 'load-balancer-api-external: tcp connection to ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:39:38Z"
    - latency: 8.512507ms
      message: 'load-balancer-api-external: resolved host name ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:39:38Z"
    - latency: 4.662881ms
      message: 'load-balancer-api-external: tcp connection to ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:38:38Z"
    - latency: 12.714559ms
      message: 'load-balancer-api-external: resolved host name ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:38:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:30:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-164-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-164.ec2.internal
      uid: 762c99b6-1ad4-48a0-a1d2-ffeed14ea630
    resourceVersion: "87859"
    uid: 58ed003c-fe32-49f4-8b85-5dff06a00015
  spec:
    sourcePod: network-check-source-6f8b768455-vcdhl
    targetEndpoint: ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:36:38Z"
      message: 'load-balancer-api-internal: tcp connection to ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.7628ms
      message: 'load-balancer-api-internal: tcp connection to ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:42:38Z"
    - latency: 8.566918ms
      message: 'load-balancer-api-internal: resolved host name ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:42:38Z"
    - latency: 10.574117ms
      message: 'load-balancer-api-internal: tcp connection to ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:41:38Z"
    - latency: 9.033615ms
      message: 'load-balancer-api-internal: resolved host name ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:41:38Z"
    - latency: 4.602798ms
      message: 'load-balancer-api-internal: tcp connection to ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:40:38Z"
    - latency: 10.836863ms
      message: 'load-balancer-api-internal: resolved host name ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:40:38Z"
    - latency: 5.087071ms
      message: 'load-balancer-api-internal: tcp connection to ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:39:38Z"
    - latency: 8.461624ms
      message: 'load-balancer-api-internal: resolved host name ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:39:38Z"
    - latency: 4.682453ms
      message: 'load-balancer-api-internal: tcp connection to ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:38:38Z"
    - latency: 12.776742ms
      message: 'load-balancer-api-internal: resolved host name ad3aae3ec4526451c850d56ff3ddc436-7e4eb4ed06a6668f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:38:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:30:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-164-to-network-check-target-ip-10-0-128-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-164.ec2.internal
      uid: 762c99b6-1ad4-48a0-a1d2-ffeed14ea630
    resourceVersion: "85899"
    uid: cccc6b66-8113-41f3-a7f9-4bb5dbafad63
  spec:
    sourcePod: network-check-source-6f8b768455-vcdhl
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:37:38Z"
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.231939ms
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:40:38Z"
    - latency: 2.218188ms
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:39:38Z"
    - latency: 1.97138ms
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:38:38Z"
    - latency: 2.315929ms
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:37:38Z"
    - latency: 2.7703ms
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:36:38Z"
    - latency: 2.088047ms
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:35:38Z"
    - latency: 2.198793ms
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:34:38Z"
    - latency: 2.381747ms
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:33:38Z"
    - latency: 2.173389ms
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:32:38Z"
    - latency: 2.143065ms
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:31:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:30:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-164-to-network-check-target-ip-10-0-136-122
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-164.ec2.internal
      uid: 762c99b6-1ad4-48a0-a1d2-ffeed14ea630
    resourceVersion: "85900"
    uid: 84b83c9f-e850-4212-a0c2-95a628c20d3d
  spec:
    sourcePod: network-check-source-6f8b768455-vcdhl
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:37:38Z"
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.410304ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:40:38Z"
    - latency: 2.791815ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:39:38Z"
    - latency: 2.476589ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:38:38Z"
    - latency: 2.613448ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:37:38Z"
    - latency: 2.762404ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:36:38Z"
    - latency: 2.701621ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:35:38Z"
    - latency: 2.260917ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:34:38Z"
    - latency: 2.648551ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:33:38Z"
    - latency: 2.629566ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:32:38Z"
    - latency: 2.512568ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:31:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:30:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-164-to-network-check-target-ip-10-0-142-164
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-164.ec2.internal
      uid: 762c99b6-1ad4-48a0-a1d2-ffeed14ea630
    resourceVersion: "85898"
    uid: c8f5d777-be68-4a36-aa74-6d6c1557bdb2
  spec:
    sourcePod: network-check-source-6f8b768455-vcdhl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:37:38Z"
      message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 819.064µs
      message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:40:38Z"
    - latency: 1.187259ms
      message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:39:38Z"
    - latency: 927.906µs
      message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:38:38Z"
    - latency: 903.487µs
      message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:37:38Z"
    - latency: 816.714µs
      message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:36:38Z"
    - latency: 854.151µs
      message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:35:38Z"
    - latency: 967.285µs
      message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:34:38Z"
    - latency: 1.050135ms
      message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:33:38Z"
    - latency: 1.124295ms
      message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:32:38Z"
    - latency: 1.173071ms
      message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:31:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:30:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-164-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-164.ec2.internal
      uid: 762c99b6-1ad4-48a0-a1d2-ffeed14ea630
    resourceVersion: "87858"
    uid: bc1a1af9-27e9-42ba-991b-0fb99be61bf0
  spec:
    sourcePod: network-check-source-6f8b768455-vcdhl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:36:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 918.938µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:42:38Z"
    - latency: 1.828291ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:42:38Z"
    - latency: 1.244294ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:41:38Z"
    - latency: 1.68775ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:41:38Z"
    - latency: 935.273µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:40:38Z"
    - latency: 2.194064ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:40:38Z"
    - latency: 1.176566ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:39:38Z"
    - latency: 2.288726ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:39:38Z"
    - latency: 734.73µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:38:38Z"
    - latency: 2.013686ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:38:38Z"
kind: List
metadata:
  resourceVersion: ""