apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T14:18:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-67-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-67.ec2.internal
      uid: bd0e17a0-b118-40bf-a1b3-a7a8759274a5
    resourceVersion: "43867"
    uid: 212c8838-d021-4e44-ab5b-e5c65955de1b
  spec:
    sourcePod: network-check-source-7f44b6dd87-s8hzg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T14:25:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 879.384µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:46:32Z"
    - latency: 1.107763ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:45:32Z"
    - latency: 998.983µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:44:32Z"
    - latency: 852.039µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:43:32Z"
    - latency: 716.995µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:42:32Z"
    - latency: 846.414µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:41:32Z"
    - latency: 857.423µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:40:32Z"
    - latency: 921.265µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:39:32Z"
    - latency: 734.17µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:38:32Z"
    - latency: 1.129193ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:37:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T14:18:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-67-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-67.ec2.internal
      uid: bd0e17a0-b118-40bf-a1b3-a7a8759274a5
    resourceVersion: "45993"
    uid: 9d992d31-4b88-45d8-809e-f4671708880c
  spec:
    sourcePod: network-check-source-7f44b6dd87-s8hzg
    targetEndpoint: af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T14:24:32Z"
      message: 'load-balancer-api-external: tcp connection to af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.106925ms
      message: 'load-balancer-api-external: tcp connection to af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:48:32Z"
    - latency: 5.959109ms
      message: 'load-balancer-api-external: resolved host name af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:48:32Z"
    - latency: 6.429783ms
      message: 'load-balancer-api-external: tcp connection to af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:47:32Z"
    - latency: 6.058789ms
      message: 'load-balancer-api-external: resolved host name af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:47:32Z"
    - latency: 6.10167ms
      message: 'load-balancer-api-external: tcp connection to af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:46:32Z"
    - latency: 6.048341ms
      message: 'load-balancer-api-external: resolved host name af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:46:32Z"
    - latency: 6.300674ms
      message: 'load-balancer-api-external: tcp connection to af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:45:32Z"
    - latency: 6.883609ms
      message: 'load-balancer-api-external: resolved host name af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:45:32Z"
    - latency: 6.817581ms
      message: 'load-balancer-api-external: tcp connection to af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:44:32Z"
    - latency: 7.921115ms
      message: 'load-balancer-api-external: resolved host name af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:44:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T14:18:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-67-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-67.ec2.internal
      uid: bd0e17a0-b118-40bf-a1b3-a7a8759274a5
    resourceVersion: "45992"
    uid: ad625dd8-bd97-49dc-9992-2ed06f0855fe
  spec:
    sourcePod: network-check-source-7f44b6dd87-s8hzg
    targetEndpoint: af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T14:24:32Z"
      message: 'load-balancer-api-internal: tcp connection to af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.090883ms
      message: 'load-balancer-api-internal: tcp connection to af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:48:32Z"
    - latency: 6.476275ms
      message: 'load-balancer-api-internal: resolved host name af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:48:32Z"
    - latency: 4.627905ms
      message: 'load-balancer-api-internal: tcp connection to af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:47:32Z"
    - latency: 5.949324ms
      message: 'load-balancer-api-internal: resolved host name af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:47:32Z"
    - latency: 6.22153ms
      message: 'load-balancer-api-internal: tcp connection to af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:46:32Z"
    - latency: 6.005398ms
      message: 'load-balancer-api-internal: resolved host name af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:46:32Z"
    - latency: 5.007404ms
      message: 'load-balancer-api-internal: tcp connection to af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:45:32Z"
    - latency: 6.939463ms
      message: 'load-balancer-api-internal: resolved host name af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:45:32Z"
    - latency: 6.865782ms
      message: 'load-balancer-api-internal: tcp connection to af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:44:32Z"
    - latency: 7.99494ms
      message: 'load-balancer-api-internal: resolved host name af279bb59aa9f4b65a63c3f9b7db9f10-40ad0823d9fa5cd9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:44:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T14:18:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-67-to-network-check-target-ip-10-0-131-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-67.ec2.internal
      uid: bd0e17a0-b118-40bf-a1b3-a7a8759274a5
    resourceVersion: "43865"
    uid: 4ac4ad39-ad7a-4094-bc83-ec6c89c0096f
  spec:
    sourcePod: network-check-source-7f44b6dd87-s8hzg
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T14:25:32Z"
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.400534ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:46:32Z"
    - latency: 2.238373ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:45:32Z"
    - latency: 2.906238ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:44:32Z"
    - latency: 1.891154ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:43:32Z"
    - latency: 2.056607ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:42:32Z"
    - latency: 2.436568ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:41:32Z"
    - latency: 3.4774ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:40:32Z"
    - latency: 1.810177ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:39:32Z"
    - latency: 1.968659ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:38:32Z"
    - latency: 1.998233ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:37:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T14:18:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-67-to-network-check-target-ip-10-0-134-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-67.ec2.internal
      uid: bd0e17a0-b118-40bf-a1b3-a7a8759274a5
    resourceVersion: "43866"
    uid: c44c9ee3-be58-40d9-a1f5-bcd909a0f8f9
  spec:
    sourcePod: network-check-source-7f44b6dd87-s8hzg
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T14:25:32Z"
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.158531ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:46:32Z"
    - latency: 2.330196ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:45:32Z"
    - latency: 2.613128ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:44:32Z"
    - latency: 2.279876ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:43:32Z"
    - latency: 2.144051ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:42:32Z"
    - latency: 2.413388ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:41:32Z"
    - latency: 2.155848ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:40:32Z"
    - latency: 1.826597ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:39:32Z"
    - latency: 1.967349ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:38:32Z"
    - latency: 2.205152ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:37:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T14:18:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-67-to-network-check-target-ip-10-0-143-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-67.ec2.internal
      uid: bd0e17a0-b118-40bf-a1b3-a7a8759274a5
    resourceVersion: "43864"
    uid: 07363d63-1450-489c-85be-c3dd3c3729f3
  spec:
    sourcePod: network-check-source-7f44b6dd87-s8hzg
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T14:25:32Z"
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 725.442µs
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:46:32Z"
    - latency: 723.792µs
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:45:32Z"
    - latency: 807.925µs
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:44:32Z"
    - latency: 858.527µs
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:43:32Z"
    - latency: 1.301756ms
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:42:32Z"
    - latency: 718.408µs
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:41:32Z"
    - latency: 944.296µs
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:40:32Z"
    - latency: 954.254µs
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:39:32Z"
    - latency: 888.02µs
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:38:32Z"
    - latency: 1.279381ms
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:37:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T14:18:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-67-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-67.ec2.internal
      uid: bd0e17a0-b118-40bf-a1b3-a7a8759274a5
    resourceVersion: "45991"
    uid: 79f118bf-532e-465d-b879-a4c605b2e35c
  spec:
    sourcePod: network-check-source-7f44b6dd87-s8hzg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T14:24:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.337512ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:48:32Z"
    - latency: 1.671091ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:48:32Z"
    - latency: 873.91µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:47:32Z"
    - latency: 1.367734ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:47:32Z"
    - latency: 1.043763ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:46:32Z"
    - latency: 1.698501ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:46:32Z"
    - latency: 780.959µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:45:32Z"
    - latency: 1.853019ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:45:32Z"
    - latency: 1.325484ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:44:32Z"
    - latency: 1.755872ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:44:32Z"
kind: List
metadata:
  resourceVersion: ""