apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:07:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-75-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-75.ec2.internal
      uid: 277a539f-63d1-4f71-8bbc-57a37710417a
    resourceVersion: "40174"
    uid: 5222bce4-d14e-472e-acf5-d29ac717b644
  spec:
    sourcePod: network-check-source-7f44b6dd87-q7hv5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:14:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 881.836µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:03:27Z"
    - latency: 908.642µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:02:27Z"
    - latency: 803.707µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:01:27Z"
    - latency: 1.027723ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:00:27Z"
    - latency: 861.63µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:59:27Z"
    - latency: 934.088µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:58:27Z"
    - latency: 1.182806ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:57:27Z"
    - latency: 884.475µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:56:27Z"
    - latency: 843.301µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:55:27Z"
    - latency: 1.104129ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:54:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:07:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-75-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-75.ec2.internal
      uid: 277a539f-63d1-4f71-8bbc-57a37710417a
    resourceVersion: "42335"
    uid: 4e92ad4c-2d3f-455c-8bbf-926b5c909c6a
  spec:
    sourcePod: network-check-source-7f44b6dd87-q7hv5
    targetEndpoint: a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:13:27Z"
      message: 'load-balancer-api-external: tcp connection to a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.18333ms
      message: 'load-balancer-api-external: tcp connection to a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:07:27Z"
    - latency: 6.249453ms
      message: 'load-balancer-api-external: resolved host name a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T17:07:27Z"
    - latency: 4.555623ms
      message: 'load-balancer-api-external: tcp connection to a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:06:27Z"
    - latency: 9.954173ms
      message: 'load-balancer-api-external: resolved host name a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T17:06:27Z"
    - latency: 4.188629ms
      message: 'load-balancer-api-external: tcp connection to a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:05:27Z"
    - latency: 6.544564ms
      message: 'load-balancer-api-external: resolved host name a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T17:05:27Z"
    - latency: 5.155669ms
      message: 'load-balancer-api-external: tcp connection to a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:04:27Z"
    - latency: 6.147007ms
      message: 'load-balancer-api-external: resolved host name a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T17:04:27Z"
    - latency: 5.245176ms
      message: 'load-balancer-api-external: tcp connection to a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:03:27Z"
    - latency: 6.266536ms
      message: 'load-balancer-api-external: resolved host name a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T17:03:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:07:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-75-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-75.ec2.internal
      uid: 277a539f-63d1-4f71-8bbc-57a37710417a
    resourceVersion: "42336"
    uid: 6fbc10ff-ae09-41c7-8451-8dad414b1b10
  spec:
    sourcePod: network-check-source-7f44b6dd87-q7hv5
    targetEndpoint: a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:13:27Z"
      message: 'load-balancer-api-internal: tcp connection to a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.787672ms
      message: 'load-balancer-api-internal: tcp connection to a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:07:27Z"
    - latency: 6.219144ms
      message: 'load-balancer-api-internal: resolved host name a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T17:07:27Z"
    - latency: 4.585399ms
      message: 'load-balancer-api-internal: tcp connection to a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:06:27Z"
    - latency: 9.921642ms
      message: 'load-balancer-api-internal: resolved host name a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T17:06:27Z"
    - latency: 3.428518ms
      message: 'load-balancer-api-internal: tcp connection to a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:05:27Z"
    - latency: 6.483719ms
      message: 'load-balancer-api-internal: resolved host name a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T17:05:27Z"
    - latency: 4.150919ms
      message: 'load-balancer-api-internal: tcp connection to a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:04:27Z"
    - latency: 6.102532ms
      message: 'load-balancer-api-internal: resolved host name a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T17:04:27Z"
    - latency: 4.487679ms
      message: 'load-balancer-api-internal: tcp connection to a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:03:27Z"
    - latency: 6.402465ms
      message: 'load-balancer-api-internal: resolved host name a14faec65adec443b9376a6ae5e449c6-48285481bacbb496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T17:03:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:07:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-75-to-network-check-target-ip-10-0-130-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-75.ec2.internal
      uid: 277a539f-63d1-4f71-8bbc-57a37710417a
    resourceVersion: "40173"
    uid: 7af0e7a6-d906-41e1-ab0d-123d116877c7
  spec:
    sourcePod: network-check-source-7f44b6dd87-q7hv5
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:14:27Z"
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.10742ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:03:27Z"
    - latency: 2.364459ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:02:27Z"
    - latency: 1.796017ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:01:27Z"
    - latency: 2.348325ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:00:27Z"
    - latency: 2.051033ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:59:27Z"
    - latency: 1.917802ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:58:27Z"
    - latency: 2.170819ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:57:27Z"
    - latency: 2.243103ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:56:27Z"
    - latency: 2.116721ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:55:27Z"
    - latency: 2.190228ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:54:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:07:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-75-to-network-check-target-ip-10-0-136-75
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-75.ec2.internal
      uid: 277a539f-63d1-4f71-8bbc-57a37710417a
    resourceVersion: "40171"
    uid: ad2ef362-7b6e-4f61-8f7f-e7a6f2fd3ed2
  spec:
    sourcePod: network-check-source-7f44b6dd87-q7hv5
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:14:27Z"
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 777.673µs
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:03:27Z"
    - latency: 1.127164ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:02:27Z"
    - latency: 727.822µs
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:01:27Z"
    - latency: 681.031µs
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:00:27Z"
    - latency: 844.866µs
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:59:27Z"
    - latency: 1.116721ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:58:27Z"
    - latency: 1.206958ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:57:27Z"
    - latency: 725.878µs
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:56:27Z"
    - latency: 1.059612ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:55:27Z"
    - latency: 935.962µs
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:54:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:07:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-75-to-network-check-target-ip-10-0-140-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-75.ec2.internal
      uid: 277a539f-63d1-4f71-8bbc-57a37710417a
    resourceVersion: "40172"
    uid: 2bfcae63-134b-4521-9330-99cdef22e69b
  spec:
    sourcePod: network-check-source-7f44b6dd87-q7hv5
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:14:27Z"
      message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.101701ms
      message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:03:27Z"
    - latency: 1.958035ms
      message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:02:27Z"
    - latency: 1.767444ms
      message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:01:27Z"
    - latency: 1.862603ms
      message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:00:27Z"
    - latency: 1.881965ms
      message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:59:27Z"
    - latency: 1.946887ms
      message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:58:27Z"
    - latency: 1.846708ms
      message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:57:27Z"
    - latency: 1.946604ms
      message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:56:27Z"
    - latency: 1.770036ms
      message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:55:27Z"
    - latency: 1.970082ms
      message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:54:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:07:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-75-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-75.ec2.internal
      uid: 277a539f-63d1-4f71-8bbc-57a37710417a
    resourceVersion: "42334"
    uid: 38e61c88-3f9d-4516-85a0-b4dcaa5694b2
  spec:
    sourcePod: network-check-source-7f44b6dd87-q7hv5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:13:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 825.839µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:07:27Z"
    - latency: 1.627798ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T17:07:27Z"
    - latency: 1.074033ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:06:27Z"
    - latency: 1.73887ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T17:06:27Z"
    - latency: 767.227µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:05:27Z"
    - latency: 1.825172ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T17:05:27Z"
    - latency: 1.184292ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:04:27Z"
    - latency: 1.578896ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T17:04:27Z"
    - latency: 817.033µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T17:03:27Z"
    - latency: 1.652601ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T17:03:27Z"
kind: List
metadata:
  resourceVersion: ""