apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:12:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-115-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-115.ec2.internal
      uid: 707070fa-2e38-45f2-bc5b-e7b99e471be3
    resourceVersion: "64163"
    uid: 882be977-b2b0-491f-8c34-6e4a5b2d96bf
  spec:
    sourcePod: network-check-source-7d88cb55d8-9jjrt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:19:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.174468ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:54:39Z"
    - latency: 1.246208ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:53:39Z"
    - latency: 1.104815ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:52:39Z"
    - latency: 1.056193ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:51:39Z"
    - latency: 1.158617ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:50:39Z"
    - latency: 1.228225ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:49:39Z"
    - latency: 1.290657ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:48:39Z"
    - latency: 1.073112ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:47:39Z"
    - latency: 1.220793ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:46:39Z"
    - latency: 1.307678ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:45:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:12:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-115-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-115.ec2.internal
      uid: 707070fa-2e38-45f2-bc5b-e7b99e471be3
    resourceVersion: "64164"
    uid: 6f94cfdf-ee96-4692-8d87-867e05602c4b
  spec:
    sourcePod: network-check-source-7d88cb55d8-9jjrt
    targetEndpoint: afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:18:39Z"
      message: 'load-balancer-api-external: tcp connection to afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.451107ms
      message: 'load-balancer-api-external: tcp connection to afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:54:39Z"
    - latency: 8.29078ms
      message: 'load-balancer-api-external: resolved host name afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:54:39Z"
    - latency: 5.239283ms
      message: 'load-balancer-api-external: tcp connection to afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:53:39Z"
    - latency: 7.582126ms
      message: 'load-balancer-api-external: resolved host name afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:53:39Z"
    - latency: 5.28086ms
      message: 'load-balancer-api-external: tcp connection to afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:52:39Z"
    - latency: 7.310985ms
      message: 'load-balancer-api-external: resolved host name afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:52:39Z"
    - latency: 4.737621ms
      message: 'load-balancer-api-external: tcp connection to afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:51:39Z"
    - latency: 7.387404ms
      message: 'load-balancer-api-external: resolved host name afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:51:39Z"
    - latency: 3.89216ms
      message: 'load-balancer-api-external: tcp connection to afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:50:39Z"
    - latency: 7.219028ms
      message: 'load-balancer-api-external: resolved host name afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:50:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:12:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-115-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-115.ec2.internal
      uid: 707070fa-2e38-45f2-bc5b-e7b99e471be3
    resourceVersion: "64165"
    uid: d9e49258-9574-428e-ba38-8af0ead41027
  spec:
    sourcePod: network-check-source-7d88cb55d8-9jjrt
    targetEndpoint: afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:18:39Z"
      message: 'load-balancer-api-internal: tcp connection to afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.375791ms
      message: 'load-balancer-api-internal: tcp connection to afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:54:39Z"
    - latency: 8.248387ms
      message: 'load-balancer-api-internal: resolved host name afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:54:39Z"
    - latency: 5.243336ms
      message: 'load-balancer-api-internal: tcp connection to afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:53:39Z"
    - latency: 7.561853ms
      message: 'load-balancer-api-internal: resolved host name afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:53:39Z"
    - latency: 3.34582ms
      message: 'load-balancer-api-internal: tcp connection to afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:52:39Z"
    - latency: 7.379945ms
      message: 'load-balancer-api-internal: resolved host name afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:52:39Z"
    - latency: 5.16594ms
      message: 'load-balancer-api-internal: tcp connection to afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:51:39Z"
    - latency: 7.419238ms
      message: 'load-balancer-api-internal: resolved host name afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:51:39Z"
    - latency: 3.894436ms
      message: 'load-balancer-api-internal: tcp connection to afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:50:39Z"
    - latency: 7.337509ms
      message: 'load-balancer-api-internal: resolved host name afee0e41bdf9c476ab87d03d44ebbf98-c8f2ceff41d218c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:50:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:12:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-115-to-network-check-target-ip-10-0-132-115
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-115.ec2.internal
      uid: 707070fa-2e38-45f2-bc5b-e7b99e471be3
    resourceVersion: "64159"
    uid: 5d4f9c85-72b3-435e-87d9-1a920e031e3e
  spec:
    sourcePod: network-check-source-7d88cb55d8-9jjrt
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:19:39Z"
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.087149ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:54:39Z"
    - latency: 1.912733ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:53:39Z"
    - latency: 1.648247ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:52:39Z"
    - latency: 1.441792ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:51:39Z"
    - latency: 966.657µs
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:50:39Z"
    - latency: 1.038092ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:49:39Z"
    - latency: 1.120386ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:48:39Z"
    - latency: 953.726µs
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:47:39Z"
    - latency: 1.008222ms
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:46:39Z"
    - latency: 884.423µs
      message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:45:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:12:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-115-to-network-check-target-ip-10-0-137-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-115.ec2.internal
      uid: 707070fa-2e38-45f2-bc5b-e7b99e471be3
    resourceVersion: "64161"
    uid: 074f35f7-8632-4426-97a6-56dade5c6c19
  spec:
    sourcePod: network-check-source-7d88cb55d8-9jjrt
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:19:39Z"
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.529741ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:54:39Z"
    - latency: 3.09154ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:53:39Z"
    - latency: 2.46179ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:52:39Z"
    - latency: 2.269333ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:51:39Z"
    - latency: 2.423506ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:50:39Z"
    - latency: 2.42555ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:49:39Z"
    - latency: 2.509878ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:48:39Z"
    - latency: 2.518601ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:47:39Z"
    - latency: 2.450332ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:46:39Z"
    - latency: 2.350598ms
      message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:45:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:12:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-115-to-network-check-target-ip-10-0-140-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-115.ec2.internal
      uid: 707070fa-2e38-45f2-bc5b-e7b99e471be3
    resourceVersion: "64160"
    uid: 85233864-cd07-41d5-89a5-50796c268868
  spec:
    sourcePod: network-check-source-7d88cb55d8-9jjrt
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:19:39Z"
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.247981ms
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:54:39Z"
    - latency: 2.276193ms
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:53:39Z"
    - latency: 2.349097ms
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:52:39Z"
    - latency: 2.180358ms
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:51:39Z"
    - latency: 2.375685ms
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:50:39Z"
    - latency: 2.501999ms
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:49:39Z"
    - latency: 2.448955ms
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:48:39Z"
    - latency: 2.513535ms
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:47:39Z"
    - latency: 2.44538ms
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:46:39Z"
    - latency: 2.379963ms
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:45:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:12:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-115-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-115.ec2.internal
      uid: 707070fa-2e38-45f2-bc5b-e7b99e471be3
    resourceVersion: "64162"
    uid: fa9e942f-ff8d-44be-b937-1da29d06eeaf
  spec:
    sourcePod: network-check-source-7d88cb55d8-9jjrt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:18:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.094777ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:54:39Z"
    - latency: 1.930407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:54:39Z"
    - latency: 1.064628ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:53:39Z"
    - latency: 2.06707ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:53:39Z"
    - latency: 689.121µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:52:39Z"
    - latency: 1.712355ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:52:39Z"
    - latency: 1.098883ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:51:39Z"
    - latency: 2.223765ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:51:39Z"
    - latency: 1.457904ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:50:39Z"
    - latency: 1.907914ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:50:39Z"
kind: List
metadata:
  resourceVersion: ""