apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:55:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-101-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-101.ec2.internal
      uid: 93f1b50d-d9e9-4ee6-916a-6a4fe8edc690
    resourceVersion: "42997"
    uid: 3d265f43-448a-465d-88dd-31687141daf3
  spec:
    sourcePod: network-check-source-7f44b6dd87-7ptz7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T17:02:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.120175ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:23:05Z"
    - latency: 909.803µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:22:05Z"
    - latency: 852.326µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:21:05Z"
    - latency: 1.153897ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:20:05Z"
    - latency: 1.020677ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:19:05Z"
    - latency: 928.442µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:18:05Z"
    - latency: 877.188µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:17:05Z"
    - latency: 1.109656ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:16:05Z"
    - latency: 1.203491ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:15:05Z"
    - latency: 818.524µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:14:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:55:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-101-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-101.ec2.internal
      uid: 93f1b50d-d9e9-4ee6-916a-6a4fe8edc690
    resourceVersion: "45113"
    uid: fdd47941-7a98-44ab-a235-45b93c7ba4ae
  spec:
    sourcePod: network-check-source-7f44b6dd87-7ptz7
    targetEndpoint: af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T17:01:05Z"
      message: 'load-balancer-api-external: tcp connection to af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.341289ms
      message: 'load-balancer-api-external: tcp connection to af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:25:05Z"
    - latency: 10.723289ms
      message: 'load-balancer-api-external: resolved host name af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:25:05Z"
    - latency: 3.432789ms
      message: 'load-balancer-api-external: tcp connection to af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:24:05Z"
    - latency: 7.805413ms
      message: 'load-balancer-api-external: resolved host name af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:24:05Z"
    - latency: 7.160906ms
      message: 'load-balancer-api-external: tcp connection to af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:23:05Z"
    - latency: 6.892523ms
      message: 'load-balancer-api-external: resolved host name af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:23:05Z"
    - latency: 2.94643ms
      message: 'load-balancer-api-external: tcp connection to af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:22:05Z"
    - latency: 8.218907ms
      message: 'load-balancer-api-external: resolved host name af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:22:05Z"
    - latency: 4.286576ms
      message: 'load-balancer-api-external: tcp connection to af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:21:05Z"
    - latency: 8.105693ms
      message: 'load-balancer-api-external: resolved host name af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:21:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:55:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-101-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-101.ec2.internal
      uid: 93f1b50d-d9e9-4ee6-916a-6a4fe8edc690
    resourceVersion: "45112"
    uid: 3c5f28f0-eab8-497b-b497-f34508f57c08
  spec:
    sourcePod: network-check-source-7f44b6dd87-7ptz7
    targetEndpoint: af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T17:01:05Z"
      message: 'load-balancer-api-internal: tcp connection to af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.095979ms
      message: 'load-balancer-api-internal: tcp connection to af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:25:05Z"
    - latency: 10.780627ms
      message: 'load-balancer-api-internal: resolved host name af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:25:05Z"
    - latency: 5.300183ms
      message: 'load-balancer-api-internal: tcp connection to af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:24:05Z"
    - latency: 7.716366ms
      message: 'load-balancer-api-internal: resolved host name af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:24:05Z"
    - latency: 5.616855ms
      message: 'load-balancer-api-internal: tcp connection to af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:23:05Z"
    - latency: 6.913968ms
      message: 'load-balancer-api-internal: resolved host name af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:23:05Z"
    - latency: 2.982657ms
      message: 'load-balancer-api-internal: tcp connection to af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:22:05Z"
    - latency: 8.252107ms
      message: 'load-balancer-api-internal: resolved host name af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:22:05Z"
    - latency: 4.301821ms
      message: 'load-balancer-api-internal: tcp connection to af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:21:05Z"
    - latency: 8.126859ms
      message: 'load-balancer-api-internal: resolved host name af07e2104b2174bb78eab8b637731ae3-2bc3d6e6d8dbfbda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:21:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:55:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-101-to-network-check-target-ip-10-0-133-151
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-101.ec2.internal
      uid: 93f1b50d-d9e9-4ee6-916a-6a4fe8edc690
    resourceVersion: "42994"
    uid: 70ae5eff-4a68-4342-a7fe-17ff139986cb
  spec:
    sourcePod: network-check-source-7f44b6dd87-7ptz7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T17:02:05Z"
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.722622ms
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:23:05Z"
    - latency: 1.787303ms
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:22:05Z"
    - latency: 1.865576ms
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:21:05Z"
    - latency: 1.869215ms
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:20:05Z"
    - latency: 1.915619ms
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:19:05Z"
    - latency: 1.687039ms
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:18:05Z"
    - latency: 1.752208ms
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:17:05Z"
    - latency: 2.09709ms
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:16:05Z"
    - latency: 2.078629ms
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:15:05Z"
    - latency: 1.950408ms
      message: 'network-check-target-ip-10-0-133-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:14:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:55:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-101-to-network-check-target-ip-10-0-135-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-101.ec2.internal
      uid: 93f1b50d-d9e9-4ee6-916a-6a4fe8edc690
    resourceVersion: "42995"
    uid: 79057404-03af-4034-bd29-fdd874d51a3d
  spec:
    sourcePod: network-check-source-7f44b6dd87-7ptz7
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T17:02:05Z"
      message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 833.878µs
      message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:23:05Z"
    - latency: 752.786µs
      message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:22:05Z"
    - latency: 821.71µs
      message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:21:05Z"
    - latency: 1.361497ms
      message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:20:05Z"
    - latency: 871.547µs
      message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:19:05Z"
    - latency: 822.879µs
      message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:18:05Z"
    - latency: 911.165µs
      message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:17:05Z"
    - latency: 767.811µs
      message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:16:05Z"
    - latency: 855.254µs
      message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:15:05Z"
    - latency: 1.222069ms
      message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:14:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:55:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-101-to-network-check-target-ip-10-0-143-164
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-101.ec2.internal
      uid: 93f1b50d-d9e9-4ee6-916a-6a4fe8edc690
    resourceVersion: "42996"
    uid: ef9f4239-439f-4e5a-af32-2cb16fdbe6f9
  spec:
    sourcePod: network-check-source-7f44b6dd87-7ptz7
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T17:02:05Z"
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.131055ms
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:23:05Z"
    - latency: 2.1798ms
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:22:05Z"
    - latency: 2.141071ms
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:21:05Z"
    - latency: 2.114922ms
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:20:05Z"
    - latency: 2.063764ms
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:19:05Z"
    - latency: 1.986932ms
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:18:05Z"
    - latency: 2.031787ms
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:17:05Z"
    - latency: 2.312768ms
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:16:05Z"
    - latency: 2.104764ms
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:15:05Z"
    - latency: 2.473916ms
      message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:14:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:55:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-101-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-101.ec2.internal
      uid: 93f1b50d-d9e9-4ee6-916a-6a4fe8edc690
    resourceVersion: "45111"
    uid: e861617a-8398-438c-8ade-00e3845ed188
  spec:
    sourcePod: network-check-source-7f44b6dd87-7ptz7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T17:01:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.200836ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:25:05Z"
    - latency: 1.748897ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:25:05Z"
    - latency: 791.091µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:24:05Z"
    - latency: 1.720402ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:24:05Z"
    - latency: 801.081µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:23:05Z"
    - latency: 1.762564ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:23:05Z"
    - latency: 817.437µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:22:05Z"
    - latency: 1.814404ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:22:05Z"
    - latency: 766.202µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:21:05Z"
    - latency: 2.10459ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:21:05Z"
kind: List
metadata:
  resourceVersion: ""