apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T09:15:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: a445d002-a025-4594-890b-75b1d2e8cf36
    resourceVersion: "67345"
    uid: 4cd925a6-d6ff-44ba-aa00-650419542c35
  spec:
    sourcePod: network-check-source-7cbc45fddc-cz8gt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T09:22:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.240893ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:50:02Z"
    - latency: 756.389µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:49:02Z"
    - latency: 1.3316ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:48:02Z"
    - latency: 1.648185ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:47:02Z"
    - latency: 948.38µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:46:02Z"
    - latency: 880.611µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:45:02Z"
    - latency: 1.273578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:44:02Z"
    - latency: 836.502µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:43:02Z"
    - latency: 1.531834ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:42:02Z"
    - latency: 887.478µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:41:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T09:15:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: a445d002-a025-4594-890b-75b1d2e8cf36
    resourceVersion: "68041"
    uid: 8a3ab51d-fabb-493e-9e19-004f3c90d8cd
  spec:
    sourcePod: network-check-source-7cbc45fddc-cz8gt
    targetEndpoint: afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T09:21:02Z"
      message: 'load-balancer-api-external: tcp connection to afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 13.418551ms
      message: 'load-balancer-api-external: tcp connection to afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:51:02Z"
    - latency: 9.375015ms
      message: 'load-balancer-api-external: resolved host name afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:51:02Z"
    - latency: 3.626702ms
      message: 'load-balancer-api-external: tcp connection to afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:50:02Z"
    - latency: 11.103399ms
      message: 'load-balancer-api-external: resolved host name afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:50:02Z"
    - latency: 3.601784ms
      message: 'load-balancer-api-external: tcp connection to afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:49:02Z"
    - latency: 8.91174ms
      message: 'load-balancer-api-external: resolved host name afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:49:02Z"
    - latency: 5.110878ms
      message: 'load-balancer-api-external: tcp connection to afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:48:02Z"
    - latency: 7.958605ms
      message: 'load-balancer-api-external: resolved host name afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:48:02Z"
    - latency: 6.084367ms
      message: 'load-balancer-api-external: tcp connection to afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:47:02Z"
    - latency: 10.955116ms
      message: 'load-balancer-api-external: resolved host name afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:47:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T09:15:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: a445d002-a025-4594-890b-75b1d2e8cf36
    resourceVersion: "68042"
    uid: bd966a6e-1498-4626-ad4c-0113c3e63442
  spec:
    sourcePod: network-check-source-7cbc45fddc-cz8gt
    targetEndpoint: afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T09:21:02Z"
      message: 'load-balancer-api-internal: tcp connection to afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.18236ms
      message: 'load-balancer-api-internal: tcp connection to afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:51:02Z"
    - latency: 9.296417ms
      message: 'load-balancer-api-internal: resolved host name afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:51:02Z"
    - latency: 3.714633ms
      message: 'load-balancer-api-internal: tcp connection to afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:50:02Z"
    - latency: 11.012326ms
      message: 'load-balancer-api-internal: resolved host name afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:50:02Z"
    - latency: 4.891362ms
      message: 'load-balancer-api-internal: tcp connection to afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:49:02Z"
    - latency: 9.06415ms
      message: 'load-balancer-api-internal: resolved host name afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:49:02Z"
    - latency: 5.288198ms
      message: 'load-balancer-api-internal: tcp connection to afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:48:02Z"
    - latency: 7.928633ms
      message: 'load-balancer-api-internal: resolved host name afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:48:02Z"
    - latency: 6.08129ms
      message: 'load-balancer-api-internal: tcp connection to afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:47:02Z"
    - latency: 10.907029ms
      message: 'load-balancer-api-internal: resolved host name afd9752e9dc6148a89261c2c85ac2572-f18e67381151058f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:47:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T09:15:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-network-check-target-ip-10-0-131-218
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: a445d002-a025-4594-890b-75b1d2e8cf36
    resourceVersion: "67344"
    uid: cc6b5b09-a76d-4e7d-8c0b-aee86ca604b4
  spec:
    sourcePod: network-check-source-7cbc45fddc-cz8gt
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T09:22:02Z"
      message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.470058ms
      message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:50:02Z"
    - latency: 2.176214ms
      message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:49:02Z"
    - latency: 2.445342ms
      message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:48:02Z"
    - latency: 2.248303ms
      message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:47:02Z"
    - latency: 2.417576ms
      message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:46:02Z"
    - latency: 2.52499ms
      message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:45:02Z"
    - latency: 2.505634ms
      message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:44:02Z"
    - latency: 2.327415ms
      message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:43:02Z"
    - latency: 2.338681ms
      message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:42:02Z"
    - latency: 2.300992ms
      message: 'network-check-target-ip-10-0-131-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:41:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T09:15:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-network-check-target-ip-10-0-132-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: a445d002-a025-4594-890b-75b1d2e8cf36
    resourceVersion: "67342"
    uid: 0768ea28-dee7-4ab2-8a1e-1207a801f350
  spec:
    sourcePod: network-check-source-7cbc45fddc-cz8gt
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T09:22:02Z"
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.209643ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:50:02Z"
    - latency: 807.5µs
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:49:02Z"
    - latency: 1.595564ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:48:02Z"
    - latency: 2.028841ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:47:02Z"
    - latency: 961.038µs
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:46:02Z"
    - latency: 1.663107ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:45:02Z"
    - latency: 976.955µs
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:44:02Z"
    - latency: 1.126686ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:43:02Z"
    - latency: 1.156373ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:42:02Z"
    - latency: 1.145796ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:41:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T09:15:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-network-check-target-ip-10-0-141-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: a445d002-a025-4594-890b-75b1d2e8cf36
    resourceVersion: "67343"
    uid: 65498e1c-cd4b-4059-b6c5-89fbafffec73
  spec:
    sourcePod: network-check-source-7cbc45fddc-cz8gt
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T09:22:02Z"
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.179596ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:50:02Z"
    - latency: 1.76452ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:49:02Z"
    - latency: 1.699798ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:48:02Z"
    - latency: 1.870866ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:47:02Z"
    - latency: 1.941303ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:46:02Z"
    - latency: 1.64067ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:45:02Z"
    - latency: 1.905099ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:44:02Z"
    - latency: 2.037333ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:43:02Z"
    - latency: 1.819248ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:42:02Z"
    - latency: 1.667981ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:41:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T09:15:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-57-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-57.ec2.internal
      uid: a445d002-a025-4594-890b-75b1d2e8cf36
    resourceVersion: "68040"
    uid: 160cdc1b-2053-4b09-843f-ab6b6ab00c18
  spec:
    sourcePod: network-check-source-7cbc45fddc-cz8gt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T09:21:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.11147ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:51:02Z"
    - latency: 1.86265ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:51:02Z"
    - latency: 1.074657ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:50:02Z"
    - latency: 2.180736ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:50:02Z"
    - latency: 1.034221ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:49:02Z"
    - latency: 2.123174ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:49:02Z"
    - latency: 1.15579ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:48:02Z"
    - latency: 1.985429ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:48:02Z"
    - latency: 944.27µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:47:02Z"
    - latency: 2.738168ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:47:02Z"
kind: List
metadata:
  resourceVersion: ""