apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:35:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-217-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-217.us-east-2.compute.internal
      uid: c08b6cfe-cc85-419d-9c3c-b6e2e1dc43f4
    resourceVersion: "70719"
    uid: 8a618f82-a30a-4d2d-acbd-240b423130ee
  spec:
    sourcePod: network-check-source-6f78d59f99-j5zl7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:42:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.713612ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:03:52Z"
    - latency: 1.35426ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:02:52Z"
    - latency: 3.619457ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:01:52Z"
    - latency: 1.074102ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:00:52Z"
    - latency: 1.170102ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:59:52Z"
    - latency: 1.156627ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:58:52Z"
    - latency: 1.246016ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:57:52Z"
    - latency: 1.047007ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:56:52Z"
    - latency: 1.254102ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:55:52Z"
    - latency: 1.411387ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:54:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:35:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-217-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-217.us-east-2.compute.internal
      uid: c08b6cfe-cc85-419d-9c3c-b6e2e1dc43f4
    resourceVersion: "71936"
    uid: 044d581b-9d7d-412c-86b8-52fac844b987
  spec:
    sourcePod: network-check-source-6f78d59f99-j5zl7
    targetEndpoint: a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:41:52Z"
      message: 'load-balancer-api-external: tcp connection to a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.982776ms
      message: 'load-balancer-api-external: tcp connection to a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:05:52Z"
    - latency: 7.376607ms
      message: 'load-balancer-api-external: resolved host name a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:05:52Z"
    - latency: 4.98657ms
      message: 'load-balancer-api-external: tcp connection to a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:04:52Z"
    - latency: 6.973351ms
      message: 'load-balancer-api-external: resolved host name a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:04:52Z"
    - latency: 33.416121ms
      message: 'load-balancer-api-external: tcp connection to a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:03:52Z"
    - latency: 77.538787ms
      message: 'load-balancer-api-external: resolved host name a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:03:52Z"
    - latency: 4.992981ms
      message: 'load-balancer-api-external: tcp connection to a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:02:52Z"
    - latency: 9.98048ms
      message: 'load-balancer-api-external: resolved host name a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:02:52Z"
    - latency: 5.658758ms
      message: 'load-balancer-api-external: tcp connection to a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:01:52Z"
    - latency: 12.751414ms
      message: 'load-balancer-api-external: resolved host name a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:01:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:35:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-217-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-217.us-east-2.compute.internal
      uid: c08b6cfe-cc85-419d-9c3c-b6e2e1dc43f4
    resourceVersion: "71935"
    uid: 0e5918c2-14a5-4d0c-b774-d8e031eeb741
  spec:
    sourcePod: network-check-source-6f78d59f99-j5zl7
    targetEndpoint: a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:41:52Z"
      message: 'load-balancer-api-internal: tcp connection to a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.052954ms
      message: 'load-balancer-api-internal: tcp connection to a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:05:52Z"
    - latency: 7.264499ms
      message: 'load-balancer-api-internal: resolved host name a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:05:52Z"
    - latency: 4.931611ms
      message: 'load-balancer-api-internal: tcp connection to a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:04:52Z"
    - latency: 6.855907ms
      message: 'load-balancer-api-internal: resolved host name a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:04:52Z"
    - latency: 21.23906ms
      message: 'load-balancer-api-internal: tcp connection to a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:03:52Z"
    - latency: 76.658519ms
      message: 'load-balancer-api-internal: resolved host name a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:03:52Z"
    - latency: 5.12893ms
      message: 'load-balancer-api-internal: tcp connection to a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:02:52Z"
    - latency: 10.002531ms
      message: 'load-balancer-api-internal: resolved host name a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:02:52Z"
    - latency: 5.648056ms
      message: 'load-balancer-api-internal: tcp connection to a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:01:52Z"
    - latency: 11.764408ms
      message: 'load-balancer-api-internal: resolved host name a393a992fa71c4698b60b799389088fc-5b56a3a318140b6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:01:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:35:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-217-to-network-check-target-ip-10-0-142-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-217.us-east-2.compute.internal
      uid: c08b6cfe-cc85-419d-9c3c-b6e2e1dc43f4
    resourceVersion: "70720"
    uid: a560c827-8e82-4ba2-9ef8-850312ce1556
  spec:
    sourcePod: network-check-source-6f78d59f99-j5zl7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:42:52Z"
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 28.694458ms
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:03:52Z"
    - latency: 1.088097ms
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:02:52Z"
    - latency: 3.459204ms
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:01:52Z"
    - latency: 1.29255ms
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:00:52Z"
    - latency: 1.636348ms
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:59:52Z"
    - latency: 1.644445ms
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:58:52Z"
    - latency: 1.218274ms
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:57:52Z"
    - latency: 1.243057ms
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:56:52Z"
    - latency: 1.048454ms
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:55:52Z"
    - latency: 1.718095ms
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:54:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:35:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-217-to-network-check-target-ip-10-0-143-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-217.us-east-2.compute.internal
      uid: c08b6cfe-cc85-419d-9c3c-b6e2e1dc43f4
    resourceVersion: "70717"
    uid: f1845f62-085c-4716-a56a-5a9f98cce749
  spec:
    sourcePod: network-check-source-6f78d59f99-j5zl7
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:42:52Z"
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 9.548701ms
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:03:52Z"
    - latency: 2.463282ms
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:02:52Z"
    - latency: 4.462936ms
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:01:52Z"
    - latency: 2.366213ms
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:00:52Z"
    - latency: 2.503489ms
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:59:52Z"
    - latency: 2.035169ms
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:58:52Z"
    - latency: 2.527807ms
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:57:52Z"
    - latency: 2.66537ms
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:56:52Z"
    - latency: 2.310724ms
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:55:52Z"
    - latency: 3.887516ms
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:54:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:35:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-217-to-network-check-target-ip-10-0-143-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-217.us-east-2.compute.internal
      uid: c08b6cfe-cc85-419d-9c3c-b6e2e1dc43f4
    resourceVersion: "70716"
    uid: c7d3d322-05d5-4309-a3e5-4950f3515925
  spec:
    sourcePod: network-check-source-6f78d59f99-j5zl7
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:42:52Z"
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 10.368083ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:03:52Z"
    - latency: 2.547277ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:02:52Z"
    - latency: 5.999512ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:01:52Z"
    - latency: 2.380079ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:00:52Z"
    - latency: 2.323252ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:59:52Z"
    - latency: 2.424627ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:58:52Z"
    - latency: 2.558652ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:57:52Z"
    - latency: 2.324433ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:56:52Z"
    - latency: 2.26798ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:55:52Z"
    - latency: 3.884557ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:54:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:35:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-217-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-217.us-east-2.compute.internal
      uid: c08b6cfe-cc85-419d-9c3c-b6e2e1dc43f4
    resourceVersion: "71934"
    uid: b5c16a4d-d461-4880-bc32-2f290b0d2d26
  spec:
    sourcePod: network-check-source-6f78d59f99-j5zl7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:41:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.14273ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:05:52Z"
    - latency: 2.022462ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:05:52Z"
    - latency: 926.983µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:04:52Z"
    - latency: 2.338491ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:04:52Z"
    - latency: 7.827078ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:03:52Z"
    - latency: 48.541118ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:03:52Z"
    - latency: 913.299µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:02:52Z"
    - latency: 1.955855ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:02:52Z"
    - latency: 1.759274ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:01:52Z"
    - latency: 5.042177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:01:52Z"
kind: List
metadata:
  resourceVersion: ""