apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T14:49:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 34a319ea-bc8d-4f5a-8cf5-9379a5112ff2
    resourceVersion: "54327"
    uid: 7af3d767-293e-4e7f-a10f-04ad46fe5ef0
  spec:
    sourcePod: network-check-source-869dcfcdcd-q47dk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T14:56:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.668648ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:24:23Z"
    - latency: 1.105743ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:23:23Z"
    - latency: 1.132512ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:22:23Z"
    - latency: 896.185µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:21:23Z"
    - latency: 1.388404ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:20:23Z"
    - latency: 1.099236ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:19:23Z"
    - latency: 1.188898ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:18:23Z"
    - latency: 967.764µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:17:23Z"
    - latency: 919.781µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:16:23Z"
    - latency: 840.569µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:15:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T14:49:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 34a319ea-bc8d-4f5a-8cf5-9379a5112ff2
    resourceVersion: "55356"
    uid: 3d637870-ccdb-42dd-926c-b2c9b5a2769d
  spec:
    sourcePod: network-check-source-869dcfcdcd-q47dk
    targetEndpoint: a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T14:55:23Z"
      message: 'load-balancer-api-external: tcp connection to a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.312348ms
      message: 'load-balancer-api-external: tcp connection to a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:25:23Z"
    - latency: 8.938803ms
      message: 'load-balancer-api-external: resolved host name a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T15:25:23Z"
    - latency: 4.086336ms
      message: 'load-balancer-api-external: tcp connection to a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:24:23Z"
    - latency: 8.657616ms
      message: 'load-balancer-api-external: resolved host name a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T15:24:23Z"
    - latency: 6.365135ms
      message: 'load-balancer-api-external: tcp connection to a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:23:23Z"
    - latency: 9.289937ms
      message: 'load-balancer-api-external: resolved host name a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T15:23:23Z"
    - latency: 3.951742ms
      message: 'load-balancer-api-external: tcp connection to a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:22:23Z"
    - latency: 7.588071ms
      message: 'load-balancer-api-external: resolved host name a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T15:22:23Z"
    - latency: 4.144477ms
      message: 'load-balancer-api-external: tcp connection to a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:21:23Z"
    - latency: 8.970428ms
      message: 'load-balancer-api-external: resolved host name a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T15:21:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T14:49:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 34a319ea-bc8d-4f5a-8cf5-9379a5112ff2
    resourceVersion: "55355"
    uid: 2fc736e1-435a-4dfc-adff-d6f5a632fdd1
  spec:
    sourcePod: network-check-source-869dcfcdcd-q47dk
    targetEndpoint: a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T14:55:23Z"
      message: 'load-balancer-api-internal: tcp connection to a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.402015ms
      message: 'load-balancer-api-internal: tcp connection to a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:25:23Z"
    - latency: 8.967762ms
      message: 'load-balancer-api-internal: resolved host name a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T15:25:23Z"
    - latency: 4.073854ms
      message: 'load-balancer-api-internal: tcp connection to a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:24:23Z"
    - latency: 8.697957ms
      message: 'load-balancer-api-internal: resolved host name a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T15:24:23Z"
    - latency: 6.274905ms
      message: 'load-balancer-api-internal: tcp connection to a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:23:23Z"
    - latency: 9.316936ms
      message: 'load-balancer-api-internal: resolved host name a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T15:23:23Z"
    - latency: 5.726683ms
      message: 'load-balancer-api-internal: tcp connection to a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:22:23Z"
    - latency: 7.689068ms
      message: 'load-balancer-api-internal: resolved host name a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T15:22:23Z"
    - latency: 5.307405ms
      message: 'load-balancer-api-internal: tcp connection to a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:21:23Z"
    - latency: 8.99903ms
      message: 'load-balancer-api-internal: resolved host name a1669c46c80234439893bcf8f5fcb590-6c18cbca401f14c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T15:21:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T14:49:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-network-check-target-ip-10-0-133-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 34a319ea-bc8d-4f5a-8cf5-9379a5112ff2
    resourceVersion: "54325"
    uid: db23d5a2-ccf5-4f17-bf64-0c587024e819
  spec:
    sourcePod: network-check-source-869dcfcdcd-q47dk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T14:56:23Z"
      message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.168147ms
      message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:24:23Z"
    - latency: 2.230845ms
      message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:23:23Z"
    - latency: 2.332702ms
      message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:22:23Z"
    - latency: 2.080945ms
      message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:21:23Z"
    - latency: 2.018377ms
      message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:20:23Z"
    - latency: 2.277369ms
      message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:19:23Z"
    - latency: 2.383747ms
      message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:18:23Z"
    - latency: 2.153301ms
      message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:17:23Z"
    - latency: 2.369769ms
      message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:16:23Z"
    - latency: 2.234954ms
      message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:15:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T14:49:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-network-check-target-ip-10-0-133-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 34a319ea-bc8d-4f5a-8cf5-9379a5112ff2
    resourceVersion: "54326"
    uid: 0d4c36e9-7f4b-4083-9583-2518953b77b5
  spec:
    sourcePod: network-check-source-869dcfcdcd-q47dk
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T14:56:23Z"
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.853891ms
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:24:23Z"
    - latency: 2.070077ms
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:23:23Z"
    - latency: 2.047488ms
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:22:23Z"
    - latency: 2.126124ms
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:21:23Z"
    - latency: 2.09763ms
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:20:23Z"
    - latency: 2.043051ms
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:19:23Z"
    - latency: 2.173519ms
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:18:23Z"
    - latency: 1.9662ms
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:17:23Z"
    - latency: 1.757634ms
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:16:23Z"
    - latency: 1.922627ms
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:15:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T14:49:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-network-check-target-ip-10-0-136-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 34a319ea-bc8d-4f5a-8cf5-9379a5112ff2
    resourceVersion: "54324"
    uid: f2eb6ac6-648a-4fa8-9b5c-dcc7bd92e716
  spec:
    sourcePod: network-check-source-869dcfcdcd-q47dk
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T14:56:23Z"
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 881.052µs
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:24:23Z"
    - latency: 884.335µs
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:23:23Z"
    - latency: 833.169µs
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:22:23Z"
    - latency: 814.698µs
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:21:23Z"
    - latency: 1.437ms
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:20:23Z"
    - latency: 886.353µs
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:19:23Z"
    - latency: 990.464µs
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:18:23Z"
    - latency: 893.862µs
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:17:23Z"
    - latency: 740.071µs
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:16:23Z"
    - latency: 1.624054ms
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:15:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T14:49:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 34a319ea-bc8d-4f5a-8cf5-9379a5112ff2
    resourceVersion: "55354"
    uid: 8757faef-bba2-4391-8dd1-e6d940ecbd71
  spec:
    sourcePod: network-check-source-869dcfcdcd-q47dk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T14:55:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.37043ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:25:23Z"
    - latency: 1.86286ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T15:25:23Z"
    - latency: 1.217353ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:24:23Z"
    - latency: 1.870592ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T15:24:23Z"
    - latency: 1.019504ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:23:23Z"
    - latency: 1.571125ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T15:23:23Z"
    - latency: 782.469µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:22:23Z"
    - latency: 1.673716ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T15:22:23Z"
    - latency: 874.837µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:21:23Z"
    - latency: 2.540773ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T15:21:23Z"
kind: List
metadata:
  resourceVersion: ""