apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:49:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-156-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-156.ec2.internal
      uid: df9a246c-9b85-4c46-b1e9-7f93a036b160
    resourceVersion: "61142"
    uid: db3b9c76-fc0d-41e8-9a99-cac7671c4e54
  spec:
    sourcePod: network-check-source-685456655f-4sjnx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:56:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.061872ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:24:40Z"
    - latency: 936.074µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:23:40Z"
    - latency: 997.977µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:22:40Z"
    - latency: 1.064144ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:21:40Z"
    - latency: 1.036845ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:20:40Z"
    - latency: 1.272473ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:19:40Z"
    - latency: 1.112882ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:18:40Z"
    - latency: 1.91626ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:17:40Z"
    - latency: 1.302411ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:16:40Z"
    - latency: 1.442905ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:15:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:49:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-156-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-156.ec2.internal
      uid: df9a246c-9b85-4c46-b1e9-7f93a036b160
    resourceVersion: "61922"
    uid: f1c0883c-2aa1-4da0-9859-4e6f414bd6ca
  spec:
    sourcePod: network-check-source-685456655f-4sjnx
    targetEndpoint: a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:55:40Z"
      message: 'load-balancer-api-external: tcp connection to a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.443381ms
      message: 'load-balancer-api-external: tcp connection to a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:25:40Z"
    - latency: 5.891003ms
      message: 'load-balancer-api-external: resolved host name a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:25:40Z"
    - latency: 4.5824ms
      message: 'load-balancer-api-external: tcp connection to a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:24:40Z"
    - latency: 7.167359ms
      message: 'load-balancer-api-external: resolved host name a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:24:40Z"
    - latency: 3.764208ms
      message: 'load-balancer-api-external: tcp connection to a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:23:40Z"
    - latency: 7.394634ms
      message: 'load-balancer-api-external: resolved host name a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:23:40Z"
    - latency: 4.473359ms
      message: 'load-balancer-api-external: tcp connection to a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:22:40Z"
    - latency: 6.986473ms
      message: 'load-balancer-api-external: resolved host name a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:22:40Z"
    - latency: 4.502928ms
      message: 'load-balancer-api-external: tcp connection to a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:21:40Z"
    - latency: 13.150361ms
      message: 'load-balancer-api-external: resolved host name a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:21:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:49:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-156-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-156.ec2.internal
      uid: df9a246c-9b85-4c46-b1e9-7f93a036b160
    resourceVersion: "61923"
    uid: 1338d1be-3b6d-435c-943d-f1c8813fef2c
  spec:
    sourcePod: network-check-source-685456655f-4sjnx
    targetEndpoint: a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:55:40Z"
      message: 'load-balancer-api-internal: tcp connection to a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.52785ms
      message: 'load-balancer-api-internal: tcp connection to a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:25:40Z"
    - latency: 6.004137ms
      message: 'load-balancer-api-internal: resolved host name a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:25:40Z"
    - latency: 5.953142ms
      message: 'load-balancer-api-internal: tcp connection to a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:24:40Z"
    - latency: 7.127886ms
      message: 'load-balancer-api-internal: resolved host name a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:24:40Z"
    - latency: 3.78103ms
      message: 'load-balancer-api-internal: tcp connection to a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:23:40Z"
    - latency: 7.419159ms
      message: 'load-balancer-api-internal: resolved host name a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:23:40Z"
    - latency: 4.504384ms
      message: 'load-balancer-api-internal: tcp connection to a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:22:40Z"
    - latency: 6.943099ms
      message: 'load-balancer-api-internal: resolved host name a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:22:40Z"
    - latency: 4.111796ms
      message: 'load-balancer-api-internal: tcp connection to a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:21:40Z"
    - latency: 13.171979ms
      message: 'load-balancer-api-internal: resolved host name a04f84217c0764deaa350ead08955e69-83a0589660af4ba1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:21:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:49:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-156-to-network-check-target-ip-10-0-128-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-156.ec2.internal
      uid: df9a246c-9b85-4c46-b1e9-7f93a036b160
    resourceVersion: "61140"
    uid: 0623c53b-c0b7-4cca-b443-6fea6c5cf816
  spec:
    sourcePod: network-check-source-685456655f-4sjnx
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:56:40Z"
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.606678ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:24:40Z"
    - latency: 2.356774ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:23:40Z"
    - latency: 2.379279ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:22:40Z"
    - latency: 2.935578ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:21:40Z"
    - latency: 2.922168ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:20:40Z"
    - latency: 2.759309ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:19:40Z"
    - latency: 2.782983ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:18:40Z"
    - latency: 2.323994ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:17:40Z"
    - latency: 2.5996ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:16:40Z"
    - latency: 2.405829ms
      message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:15:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:49:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-156-to-network-check-target-ip-10-0-134-225
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-156.ec2.internal
      uid: df9a246c-9b85-4c46-b1e9-7f93a036b160
    resourceVersion: "61141"
    uid: 783c083f-94a8-4357-a3ec-d1c0c708027a
  spec:
    sourcePod: network-check-source-685456655f-4sjnx
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:56:40Z"
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.542469ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:24:40Z"
    - latency: 2.627229ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:23:40Z"
    - latency: 2.474912ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:22:40Z"
    - latency: 2.586021ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:21:40Z"
    - latency: 2.482415ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:20:40Z"
    - latency: 2.701478ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:19:40Z"
    - latency: 2.856899ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:18:40Z"
    - latency: 2.491662ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:17:40Z"
    - latency: 2.797764ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:16:40Z"
    - latency: 2.388925ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:15:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:49:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-156-to-network-check-target-ip-10-0-142-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-156.ec2.internal
      uid: df9a246c-9b85-4c46-b1e9-7f93a036b160
    resourceVersion: "61138"
    uid: c7a40b60-eebc-42d7-9ebe-d32c164f9619
  spec:
    sourcePod: network-check-source-685456655f-4sjnx
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:56:40Z"
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.087284ms
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:24:40Z"
    - latency: 1.324424ms
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:23:40Z"
    - latency: 970.342µs
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:22:40Z"
    - latency: 1.211673ms
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:21:40Z"
    - latency: 1.05648ms
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:20:40Z"
    - latency: 1.165206ms
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:19:40Z"
    - latency: 1.400471ms
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:18:40Z"
    - latency: 1.076883ms
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:17:40Z"
    - latency: 1.082323ms
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:16:40Z"
    - latency: 1.122406ms
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:15:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:49:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-156-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-156.ec2.internal
      uid: df9a246c-9b85-4c46-b1e9-7f93a036b160
    resourceVersion: "61921"
    uid: 9c96e035-0ee7-48c9-bf52-ec9f7ee00ac0
  spec:
    sourcePod: network-check-source-685456655f-4sjnx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:55:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.139036ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:25:40Z"
    - latency: 1.893018ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:25:40Z"
    - latency: 855.521µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:24:40Z"
    - latency: 1.622597ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:24:40Z"
    - latency: 1.160167ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:23:40Z"
    - latency: 1.592732ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:23:40Z"
    - latency: 1.228955ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:22:40Z"
    - latency: 1.874818ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:22:40Z"
    - latency: 932.817µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T03:21:40Z"
    - latency: 2.044413ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T03:21:40Z"
kind: List
metadata:
  resourceVersion: ""