apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:21:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-238-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-238.ec2.internal
      uid: 80dec9f9-34fd-4345-a1a9-9506920e201b
    resourceVersion: "33000"
    uid: d8f3f87a-e87c-4e4f-9b5f-001c4e51875a
  spec:
    sourcePod: network-check-source-56499946bc-twcbv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:28:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.31986ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:03:11Z"
    - latency: 1.426265ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:02:11Z"
    - latency: 1.185879ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:01:11Z"
    - latency: 981.263µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:00:11Z"
    - latency: 1.306152ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:59:11Z"
    - latency: 1.2201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:58:11Z"
    - latency: 1.061225ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:57:11Z"
    - latency: 956.186µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:56:11Z"
    - latency: 1.047868ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:55:11Z"
    - latency: 968.766µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:54:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:21:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-238-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-238.ec2.internal
      uid: 80dec9f9-34fd-4345-a1a9-9506920e201b
    resourceVersion: "33002"
    uid: 08273b93-478a-4dc7-ba6f-9dccd1e097e9
  spec:
    sourcePod: network-check-source-56499946bc-twcbv
    targetEndpoint: adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:27:11Z"
      message: 'load-balancer-api-external: tcp connection to adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.75556ms
      message: 'load-balancer-api-external: tcp connection to adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:03:11Z"
    - latency: 9.961493ms
      message: 'load-balancer-api-external: resolved host name adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:03:11Z"
    - latency: 5.213178ms
      message: 'load-balancer-api-external: tcp connection to adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:02:11Z"
    - latency: 9.163908ms
      message: 'load-balancer-api-external: resolved host name adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:02:11Z"
    - latency: 5.52991ms
      message: 'load-balancer-api-external: tcp connection to adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:01:11Z"
    - latency: 9.752378ms
      message: 'load-balancer-api-external: resolved host name adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:01:11Z"
    - latency: 6.088717ms
      message: 'load-balancer-api-external: tcp connection to adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:00:11Z"
    - latency: 9.252727ms
      message: 'load-balancer-api-external: resolved host name adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:00:11Z"
    - latency: 6.135809ms
      message: 'load-balancer-api-external: tcp connection to adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:59:11Z"
    - latency: 8.354337ms
      message: 'load-balancer-api-external: resolved host name adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:59:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:21:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-238-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-238.ec2.internal
      uid: 80dec9f9-34fd-4345-a1a9-9506920e201b
    resourceVersion: "33001"
    uid: c009fba9-1285-45be-82c4-6a83f03e2cbe
  spec:
    sourcePod: network-check-source-56499946bc-twcbv
    targetEndpoint: adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:27:11Z"
      message: 'load-balancer-api-internal: tcp connection to adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.801589ms
      message: 'load-balancer-api-internal: tcp connection to adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:03:11Z"
    - latency: 9.935719ms
      message: 'load-balancer-api-internal: resolved host name adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:03:11Z"
    - latency: 5.270195ms
      message: 'load-balancer-api-internal: tcp connection to adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:02:11Z"
    - latency: 9.201426ms
      message: 'load-balancer-api-internal: resolved host name adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:02:11Z"
    - latency: 5.691605ms
      message: 'load-balancer-api-internal: tcp connection to adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:01:11Z"
    - latency: 9.71146ms
      message: 'load-balancer-api-internal: resolved host name adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:01:11Z"
    - latency: 6.175596ms
      message: 'load-balancer-api-internal: tcp connection to adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:00:11Z"
    - latency: 9.326674ms
      message: 'load-balancer-api-internal: resolved host name adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:00:11Z"
    - latency: 6.123729ms
      message: 'load-balancer-api-internal: tcp connection to adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:59:11Z"
    - latency: 8.211508ms
      message: 'load-balancer-api-internal: resolved host name adb985561f77840d8b7486c61f682fea-1b9d3686e38f1999.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:59:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:21:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-238-to-network-check-target-ip-10-0-131-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-238.ec2.internal
      uid: 80dec9f9-34fd-4345-a1a9-9506920e201b
    resourceVersion: "32996"
    uid: 84ebcc2c-b3eb-4c40-acf8-3d9cf56797a7
  spec:
    sourcePod: network-check-source-56499946bc-twcbv
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:28:11Z"
      message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.493157ms
      message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:03:11Z"
    - latency: 922.686µs
      message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:02:11Z"
    - latency: 1.404046ms
      message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:01:11Z"
    - latency: 805.699µs
      message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:00:11Z"
    - latency: 1.609581ms
      message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:59:11Z"
    - latency: 999.876µs
      message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:58:11Z"
    - latency: 1.125729ms
      message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:57:11Z"
    - latency: 867.982µs
      message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:56:11Z"
    - latency: 1.449002ms
      message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:55:11Z"
    - latency: 1.507959ms
      message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:54:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:21:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-238-to-network-check-target-ip-10-0-133-122
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-238.ec2.internal
      uid: 80dec9f9-34fd-4345-a1a9-9506920e201b
    resourceVersion: "32998"
    uid: 6f7b1ba7-e71e-404d-b88b-db6eb4276905
  spec:
    sourcePod: network-check-source-56499946bc-twcbv
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:28:11Z"
      message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.500363ms
      message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:03:11Z"
    - latency: 2.176539ms
      message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:02:11Z"
    - latency: 2.394994ms
      message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:01:11Z"
    - latency: 2.35063ms
      message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:00:11Z"
    - latency: 2.05845ms
      message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:59:11Z"
    - latency: 2.18281ms
      message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:58:11Z"
    - latency: 2.291987ms
      message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:57:11Z"
    - latency: 2.14144ms
      message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:56:11Z"
    - latency: 2.51349ms
      message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:55:11Z"
    - latency: 2.303081ms
      message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:54:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:21:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-238-to-network-check-target-ip-10-0-143-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-238.ec2.internal
      uid: 80dec9f9-34fd-4345-a1a9-9506920e201b
    resourceVersion: "32997"
    uid: 2d9a7af7-a072-44c6-a004-a3c5c72415b4
  spec:
    sourcePod: network-check-source-56499946bc-twcbv
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:28:11Z"
      message: 'network-check-target-ip-10-0-143-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.051449ms
      message: 'network-check-target-ip-10-0-143-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:03:11Z"
    - latency: 1.896933ms
      message: 'network-check-target-ip-10-0-143-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:02:11Z"
    - latency: 1.860721ms
      message: 'network-check-target-ip-10-0-143-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:01:11Z"
    - latency: 1.961421ms
      message: 'network-check-target-ip-10-0-143-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:00:11Z"
    - latency: 1.698879ms
      message: 'network-check-target-ip-10-0-143-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:59:11Z"
    - latency: 1.692969ms
      message: 'network-check-target-ip-10-0-143-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:58:11Z"
    - latency: 1.640334ms
      message: 'network-check-target-ip-10-0-143-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:57:11Z"
    - latency: 1.753298ms
      message: 'network-check-target-ip-10-0-143-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:56:11Z"
    - latency: 1.842986ms
      message: 'network-check-target-ip-10-0-143-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:55:11Z"
    - latency: 1.839638ms
      message: 'network-check-target-ip-10-0-143-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:54:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:21:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-238-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-238.ec2.internal
      uid: 80dec9f9-34fd-4345-a1a9-9506920e201b
    resourceVersion: "32999"
    uid: db0abb5d-dfdc-4421-a40b-4136bb68d96a
  spec:
    sourcePod: network-check-source-56499946bc-twcbv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:27:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 840.706µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:03:11Z"
    - latency: 1.943663ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:03:11Z"
    - latency: 860.507µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:02:11Z"
    - latency: 1.913314ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:02:11Z"
    - latency: 1.19253ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:01:11Z"
    - latency: 1.795535ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:01:11Z"
    - latency: 895.295µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:00:11Z"
    - latency: 1.826774ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:00:11Z"
    - latency: 847.699µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:59:11Z"
    - latency: 2.296767ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:59:11Z"
kind: List
metadata:
  resourceVersion: ""