apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:30:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-6-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-6.ec2.internal
      uid: f95c4bf7-b6bb-4930-8819-0792c0e35c2d
    resourceVersion: "18615"
    uid: 13be1eec-1530-4b2a-b82d-f9df5f309375
  spec:
    sourcePod: network-check-source-6f78d59f99-ll9q5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:37:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.280074ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:51:52Z"
    - latency: 1.21884ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:50:52Z"
    - latency: 1.378369ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:49:52Z"
    - latency: 1.185924ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:48:52Z"
    - latency: 1.129536ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:47:52Z"
    - latency: 1.924699ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:46:52Z"
    - latency: 1.18095ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:45:52Z"
    - latency: 1.258573ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:44:52Z"
    - latency: 945.525µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:43:52Z"
    - latency: 1.084454ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:42:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:30:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-6-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-6.ec2.internal
      uid: f95c4bf7-b6bb-4930-8819-0792c0e35c2d
    resourceVersion: "20122"
    uid: e3bcfd12-57cd-4917-a0d8-0748de4a3a65
  spec:
    sourcePod: network-check-source-6f78d59f99-ll9q5
    targetEndpoint: a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:36:52Z"
      message: 'load-balancer-api-external: tcp connection to a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.287623ms
      message: 'load-balancer-api-external: tcp connection to a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:54:52Z"
    - latency: 7.689905ms
      message: 'load-balancer-api-external: resolved host name a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T07:54:52Z"
    - latency: 18.422557ms
      message: 'load-balancer-api-external: tcp connection to a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:53:52Z"
    - latency: 8.310559ms
      message: 'load-balancer-api-external: resolved host name a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T07:53:52Z"
    - latency: 16.996696ms
      message: 'load-balancer-api-external: tcp connection to a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:52:52Z"
    - latency: 8.78794ms
      message: 'load-balancer-api-external: resolved host name a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T07:52:52Z"
    - latency: 17.169049ms
      message: 'load-balancer-api-external: tcp connection to a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:51:52Z"
    - latency: 9.600999ms
      message: 'load-balancer-api-external: resolved host name a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T07:51:52Z"
    - latency: 18.717153ms
      message: 'load-balancer-api-external: tcp connection to a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:50:52Z"
    - latency: 8.968891ms
      message: 'load-balancer-api-external: resolved host name a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T07:50:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:30:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-6-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-6.ec2.internal
      uid: f95c4bf7-b6bb-4930-8819-0792c0e35c2d
    resourceVersion: "20123"
    uid: 3c08cf3f-b188-473c-b8ae-7ba750d53ac0
  spec:
    sourcePod: network-check-source-6f78d59f99-ll9q5
    targetEndpoint: a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:36:52Z"
      message: 'load-balancer-api-internal: tcp connection to a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.287028ms
      message: 'load-balancer-api-internal: tcp connection to a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:54:52Z"
    - latency: 7.790424ms
      message: 'load-balancer-api-internal: resolved host name a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T07:54:52Z"
    - latency: 17.629211ms
      message: 'load-balancer-api-internal: tcp connection to a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:53:52Z"
    - latency: 8.36032ms
      message: 'load-balancer-api-internal: resolved host name a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T07:53:52Z"
    - latency: 17.789019ms
      message: 'load-balancer-api-internal: tcp connection to a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:52:52Z"
    - latency: 8.855411ms
      message: 'load-balancer-api-internal: resolved host name a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T07:52:52Z"
    - latency: 17.443452ms
      message: 'load-balancer-api-internal: tcp connection to a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:51:52Z"
    - latency: 9.662276ms
      message: 'load-balancer-api-internal: resolved host name a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T07:51:52Z"
    - latency: 18.707907ms
      message: 'load-balancer-api-internal: tcp connection to a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:50:52Z"
    - latency: 9.060788ms
      message: 'load-balancer-api-internal: resolved host name a076ef3fd56dc42cc96e06668232893f-7e3d7af086f75940.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T07:50:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:30:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-6-to-network-check-target-ip-10-0-138-234
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-6.ec2.internal
      uid: f95c4bf7-b6bb-4930-8819-0792c0e35c2d
    resourceVersion: "18612"
    uid: 5f41ef4d-3a02-48a3-bb66-a5d90a1afe4b
  spec:
    sourcePod: network-check-source-6f78d59f99-ll9q5
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:37:52Z"
      message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.359405ms
      message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:51:52Z"
    - latency: 2.819518ms
      message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:50:52Z"
    - latency: 2.391614ms
      message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:49:52Z"
    - latency: 1.987962ms
      message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:48:52Z"
    - latency: 2.231975ms
      message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:47:52Z"
    - latency: 2.191134ms
      message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:46:52Z"
    - latency: 2.361133ms
      message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:45:52Z"
    - latency: 2.233192ms
      message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:44:52Z"
    - latency: 2.331476ms
      message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:43:52Z"
    - latency: 2.347869ms
      message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:42:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:30:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-6-to-network-check-target-ip-10-0-138-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-6.ec2.internal
      uid: f95c4bf7-b6bb-4930-8819-0792c0e35c2d
    resourceVersion: "18614"
    uid: 84427e8a-ff5a-4b97-9209-6fbfd4947082
  spec:
    sourcePod: network-check-source-6f78d59f99-ll9q5
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:37:52Z"
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.030401ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:51:52Z"
    - latency: 1.934342ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:50:52Z"
    - latency: 2.00726ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:49:52Z"
    - latency: 1.903205ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:48:52Z"
    - latency: 1.797595ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:47:52Z"
    - latency: 2.383684ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:46:52Z"
    - latency: 2.012915ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:45:52Z"
    - latency: 1.863631ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:44:52Z"
    - latency: 1.95955ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:43:52Z"
    - latency: 1.942026ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:42:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:30:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-6-to-network-check-target-ip-10-0-140-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-6.ec2.internal
      uid: f95c4bf7-b6bb-4930-8819-0792c0e35c2d
    resourceVersion: "18613"
    uid: ce78063d-18ac-4f13-a2a3-47a130dd1dcd
  spec:
    sourcePod: network-check-source-6f78d59f99-ll9q5
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:37:52Z"
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.225828ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:51:52Z"
    - latency: 1.878268ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:50:52Z"
    - latency: 1.305061ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:49:52Z"
    - latency: 1.531254ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:48:52Z"
    - latency: 1.377542ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:47:52Z"
    - latency: 1.071181ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:46:52Z"
    - latency: 1.24428ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:45:52Z"
    - latency: 894.931µs
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:44:52Z"
    - latency: 1.110465ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:43:52Z"
    - latency: 2.054926ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:42:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:30:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-6-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-6.ec2.internal
      uid: f95c4bf7-b6bb-4930-8819-0792c0e35c2d
    resourceVersion: "20121"
    uid: 085be22e-2a55-4c2a-9a00-6093fe540d8f
  spec:
    sourcePod: network-check-source-6f78d59f99-ll9q5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:36:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.030985ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:54:52Z"
    - latency: 1.713432ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T07:54:52Z"
    - latency: 790.97µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:53:52Z"
    - latency: 1.84038ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T07:53:52Z"
    - latency: 1.019962ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:52:52Z"
    - latency: 1.673153ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T07:52:52Z"
    - latency: 1.291772ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:51:52Z"
    - latency: 2.802276ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T07:51:52Z"
    - latency: 1.182435ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T07:50:52Z"
    - latency: 1.893185ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T07:50:52Z"
kind: List
metadata:
  resourceVersion: ""