apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:40:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-78-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-78.ec2.internal
      uid: 625caf1f-6e90-41a9-84e8-1fb64407f875
    resourceVersion: "54922"
    uid: e55c5750-bf93-4c9a-83fd-34d55f07118e
  spec:
    sourcePod: network-check-source-989f8b8dc-pwr2g
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:47:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.029536ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:15:07Z"
    - latency: 757.248µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:14:07Z"
    - latency: 1.478868ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:13:07Z"
    - latency: 1.745356ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:12:07Z"
    - latency: 1.295808ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:11:07Z"
    - latency: 976.222µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:10:07Z"
    - latency: 1.36743ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:09:07Z"
    - latency: 1.370947ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:08:07Z"
    - latency: 984.09µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:07:07Z"
    - latency: 977.212µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:06:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:40:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-78-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-78.ec2.internal
      uid: 625caf1f-6e90-41a9-84e8-1fb64407f875
    resourceVersion: "55873"
    uid: 41dd28e8-90fa-4bcc-b04a-edcfd0360583
  spec:
    sourcePod: network-check-source-989f8b8dc-pwr2g
    targetEndpoint: a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:46:07Z"
      message: 'load-balancer-api-external: tcp connection to a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.126773ms
      message: 'load-balancer-api-external: tcp connection to a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:16:07Z"
    - latency: 6.916133ms
      message: 'load-balancer-api-external: resolved host name a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:16:07Z"
    - latency: 6.215448ms
      message: 'load-balancer-api-external: tcp connection to a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:15:07Z"
    - latency: 7.545687ms
      message: 'load-balancer-api-external: resolved host name a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:15:07Z"
    - latency: 5.250315ms
      message: 'load-balancer-api-external: tcp connection to a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:14:07Z"
    - latency: 6.949502ms
      message: 'load-balancer-api-external: resolved host name a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:14:07Z"
    - latency: 3.525054ms
      message: 'load-balancer-api-external: tcp connection to a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:13:07Z"
    - latency: 6.72741ms
      message: 'load-balancer-api-external: resolved host name a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:13:07Z"
    - latency: 6.094486ms
      message: 'load-balancer-api-external: tcp connection to a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:12:07Z"
    - latency: 8.260557ms
      message: 'load-balancer-api-external: resolved host name a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:12:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:40:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-78-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-78.ec2.internal
      uid: 625caf1f-6e90-41a9-84e8-1fb64407f875
    resourceVersion: "55872"
    uid: f03a150b-1149-451d-8340-e7c42145dd8a
  spec:
    sourcePod: network-check-source-989f8b8dc-pwr2g
    targetEndpoint: a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:46:07Z"
      message: 'load-balancer-api-internal: tcp connection to a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.690656ms
      message: 'load-balancer-api-internal: tcp connection to a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:16:07Z"
    - latency: 7.007464ms
      message: 'load-balancer-api-internal: resolved host name a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:16:07Z"
    - latency: 3.901833ms
      message: 'load-balancer-api-internal: tcp connection to a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:15:07Z"
    - latency: 7.588283ms
      message: 'load-balancer-api-internal: resolved host name a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:15:07Z"
    - latency: 5.21215ms
      message: 'load-balancer-api-internal: tcp connection to a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:14:07Z"
    - latency: 7.01508ms
      message: 'load-balancer-api-internal: resolved host name a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:14:07Z"
    - latency: 3.343169ms
      message: 'load-balancer-api-internal: tcp connection to a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:13:07Z"
    - latency: 6.745381ms
      message: 'load-balancer-api-internal: resolved host name a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:13:07Z"
    - latency: 3.483137ms
      message: 'load-balancer-api-internal: tcp connection to a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:12:07Z"
    - latency: 8.472167ms
      message: 'load-balancer-api-internal: resolved host name a8e077418bbd6421b9bfea0239c641f9-e8ea1cb343d99bdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:12:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:40:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-78-to-network-check-target-ip-10-0-131-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-78.ec2.internal
      uid: 625caf1f-6e90-41a9-84e8-1fb64407f875
    resourceVersion: "54921"
    uid: 6048d666-56a1-40a6-aeaa-aa40af0ca6f8
  spec:
    sourcePod: network-check-source-989f8b8dc-pwr2g
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:47:07Z"
      message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.223948ms
      message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:15:07Z"
    - latency: 2.077869ms
      message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:14:07Z"
    - latency: 2.30858ms
      message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:13:07Z"
    - latency: 2.634251ms
      message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:12:07Z"
    - latency: 2.081633ms
      message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:11:07Z"
    - latency: 2.131883ms
      message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:10:07Z"
    - latency: 2.543125ms
      message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:09:07Z"
    - latency: 2.465968ms
      message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:08:07Z"
    - latency: 2.236062ms
      message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:07:07Z"
    - latency: 2.238033ms
      message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:06:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:40:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-78-to-network-check-target-ip-10-0-132-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-78.ec2.internal
      uid: 625caf1f-6e90-41a9-84e8-1fb64407f875
    resourceVersion: "54919"
    uid: 112428c4-59dc-45bd-aa9a-ad18f21b0f3c
  spec:
    sourcePod: network-check-source-989f8b8dc-pwr2g
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:47:07Z"
      message: 'network-check-target-ip-10-0-132-78: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.487821ms
      message: 'network-check-target-ip-10-0-132-78: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:15:07Z"
    - latency: 1.251382ms
      message: 'network-check-target-ip-10-0-132-78: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:14:07Z"
    - latency: 1.653382ms
      message: 'network-check-target-ip-10-0-132-78: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:13:07Z"
    - latency: 945.5µs
      message: 'network-check-target-ip-10-0-132-78: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:12:07Z"
    - latency: 884.951µs
      message: 'network-check-target-ip-10-0-132-78: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:11:07Z"
    - latency: 837.06µs
      message: 'network-check-target-ip-10-0-132-78: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:10:07Z"
    - latency: 1.722644ms
      message: 'network-check-target-ip-10-0-132-78: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:09:07Z"
    - latency: 1.618251ms
      message: 'network-check-target-ip-10-0-132-78: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:08:07Z"
    - latency: 973.998µs
      message: 'network-check-target-ip-10-0-132-78: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:07:07Z"
    - latency: 1.614732ms
      message: 'network-check-target-ip-10-0-132-78: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:06:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:40:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-78-to-network-check-target-ip-10-0-134-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-78.ec2.internal
      uid: 625caf1f-6e90-41a9-84e8-1fb64407f875
    resourceVersion: "54920"
    uid: b4be985d-265b-4268-9b72-5f57fe55b97a
  spec:
    sourcePod: network-check-source-989f8b8dc-pwr2g
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:47:07Z"
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.318316ms
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:15:07Z"
    - latency: 2.110899ms
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:14:07Z"
    - latency: 2.278006ms
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:13:07Z"
    - latency: 2.282662ms
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:12:07Z"
    - latency: 2.014638ms
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:11:07Z"
    - latency: 2.104264ms
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:10:07Z"
    - latency: 2.530631ms
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:09:07Z"
    - latency: 2.539869ms
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:08:07Z"
    - latency: 1.976788ms
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:07:07Z"
    - latency: 2.226318ms
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:06:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:40:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-78-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-78.ec2.internal
      uid: 625caf1f-6e90-41a9-84e8-1fb64407f875
    resourceVersion: "55871"
    uid: fe5bdf57-26ab-497b-8965-2a678fdf5a0b
  spec:
    sourcePod: network-check-source-989f8b8dc-pwr2g
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:46:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.196436ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:16:07Z"
    - latency: 1.754578ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:16:07Z"
    - latency: 696.551µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:15:07Z"
    - latency: 2.311243ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:15:07Z"
    - latency: 1.047533ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:14:07Z"
    - latency: 1.962809ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:14:07Z"
    - latency: 1.415693ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:13:07Z"
    - latency: 2.007515ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:13:07Z"
    - latency: 1.017416ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:12:07Z"
    - latency: 1.781907ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:12:07Z"
kind: List
metadata:
  resourceVersion: ""