apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:31:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-0-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-0.ec2.internal
      uid: 01b496ec-df9b-442f-8192-dcd8b9e5d6fa
    resourceVersion: "53028"
    uid: aea5c5b7-477b-4d59-a383-065cb68d0c92
  spec:
    sourcePod: network-check-source-7d88cb55d8-fvcgl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:38:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.105918ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:55:26Z"
    - latency: 1.129756ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:54:26Z"
    - latency: 880.001µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:53:26Z"
    - latency: 1.156605ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:52:26Z"
    - latency: 1.177977ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:51:26Z"
    - latency: 1.003206ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:50:26Z"
    - latency: 1.029105ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:49:26Z"
    - latency: 1.047024ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:48:26Z"
    - latency: 981.17µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:47:26Z"
    - latency: 2.188812ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:46:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:31:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-0-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-0.ec2.internal
      uid: 01b496ec-df9b-442f-8192-dcd8b9e5d6fa
    resourceVersion: "56160"
    uid: a35cf458-08fd-443d-8c55-dd490095bd11
  spec:
    sourcePod: network-check-source-7d88cb55d8-fvcgl
    targetEndpoint: a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:37:26Z"
      message: 'load-balancer-api-external: tcp connection to a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.873497ms
      message: 'load-balancer-api-external: tcp connection to a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:01:26Z"
    - latency: 6.357216ms
      message: 'load-balancer-api-external: resolved host name a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:01:26Z"
    - latency: 4.593651ms
      message: 'load-balancer-api-external: tcp connection to a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:00:26Z"
    - latency: 6.611164ms
      message: 'load-balancer-api-external: resolved host name a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:00:26Z"
    - latency: 6.734004ms
      message: 'load-balancer-api-external: tcp connection to a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:59:26Z"
    - latency: 6.119509ms
      message: 'load-balancer-api-external: resolved host name a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:59:26Z"
    - latency: 5.766253ms
      message: 'load-balancer-api-external: tcp connection to a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:58:26Z"
    - latency: 6.712416ms
      message: 'load-balancer-api-external: resolved host name a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:58:26Z"
    - latency: 4.256077ms
      message: 'load-balancer-api-external: tcp connection to a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:57:26Z"
    - latency: 6.292378ms
      message: 'load-balancer-api-external: resolved host name a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:57:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:31:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-0-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-0.ec2.internal
      uid: 01b496ec-df9b-442f-8192-dcd8b9e5d6fa
    resourceVersion: "56159"
    uid: 26b613eb-3ed2-4a17-8464-b94e0a01d10b
  spec:
    sourcePod: network-check-source-7d88cb55d8-fvcgl
    targetEndpoint: a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:37:26Z"
      message: 'load-balancer-api-internal: tcp connection to a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.858665ms
      message: 'load-balancer-api-internal: tcp connection to a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:01:26Z"
    - latency: 6.266605ms
      message: 'load-balancer-api-internal: resolved host name a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:01:26Z"
    - latency: 4.602655ms
      message: 'load-balancer-api-internal: tcp connection to a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:00:26Z"
    - latency: 6.710933ms
      message: 'load-balancer-api-internal: resolved host name a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:00:26Z"
    - latency: 6.410278ms
      message: 'load-balancer-api-internal: tcp connection to a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:59:26Z"
    - latency: 6.200173ms
      message: 'load-balancer-api-internal: resolved host name a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:59:26Z"
    - latency: 5.936129ms
      message: 'load-balancer-api-internal: tcp connection to a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:58:26Z"
    - latency: 6.689895ms
      message: 'load-balancer-api-internal: resolved host name a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:58:26Z"
    - latency: 7.089315ms
      message: 'load-balancer-api-internal: tcp connection to a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:57:26Z"
    - latency: 6.338279ms
      message: 'load-balancer-api-internal: resolved host name a745e069749a94a5aa7b168d4a9b66b0-f6517961aad258ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:57:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:31:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-0-to-network-check-target-ip-10-0-129-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-0.ec2.internal
      uid: 01b496ec-df9b-442f-8192-dcd8b9e5d6fa
    resourceVersion: "53026"
    uid: 726675a2-dff7-4f9f-88de-1b04e69cb543
  spec:
    sourcePod: network-check-source-7d88cb55d8-fvcgl
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:38:26Z"
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.022706ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:55:26Z"
    - latency: 2.162079ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:54:26Z"
    - latency: 1.896968ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:53:26Z"
    - latency: 2.182777ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:52:26Z"
    - latency: 2.278575ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:51:26Z"
    - latency: 1.980853ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:50:26Z"
    - latency: 1.904783ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:49:26Z"
    - latency: 2.193465ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:48:26Z"
    - latency: 2.024052ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:47:26Z"
    - latency: 2.213347ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:46:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:31:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-0-to-network-check-target-ip-10-0-139-106
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-0.ec2.internal
      uid: 01b496ec-df9b-442f-8192-dcd8b9e5d6fa
    resourceVersion: "53024"
    uid: cb74b38d-c91e-40d8-a02f-ae2deefb3e4a
  spec:
    sourcePod: network-check-source-7d88cb55d8-fvcgl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:38:26Z"
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.327539ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:55:26Z"
    - latency: 2.475061ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:54:26Z"
    - latency: 2.253018ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:53:26Z"
    - latency: 2.392986ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:52:26Z"
    - latency: 2.22725ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:51:26Z"
    - latency: 2.319346ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:50:26Z"
    - latency: 2.182604ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:49:26Z"
    - latency: 2.381104ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:48:26Z"
    - latency: 1.925581ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:47:26Z"
    - latency: 2.706551ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:46:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:31:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-0-to-network-check-target-ip-10-0-140-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-0.ec2.internal
      uid: 01b496ec-df9b-442f-8192-dcd8b9e5d6fa
    resourceVersion: "53025"
    uid: 409c482f-77ac-4dd0-ba9a-562f1a694667
  spec:
    sourcePod: network-check-source-7d88cb55d8-fvcgl
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:38:26Z"
      message: 'network-check-target-ip-10-0-140-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.299265ms
      message: 'network-check-target-ip-10-0-140-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:55:26Z"
    - latency: 879.641µs
      message: 'network-check-target-ip-10-0-140-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:54:26Z"
    - latency: 817.631µs
      message: 'network-check-target-ip-10-0-140-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:53:26Z"
    - latency: 892.464µs
      message: 'network-check-target-ip-10-0-140-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:52:26Z"
    - latency: 1.334256ms
      message: 'network-check-target-ip-10-0-140-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:51:26Z"
    - latency: 893.889µs
      message: 'network-check-target-ip-10-0-140-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:50:26Z"
    - latency: 1.071237ms
      message: 'network-check-target-ip-10-0-140-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:49:26Z"
    - latency: 868.092µs
      message: 'network-check-target-ip-10-0-140-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:48:26Z"
    - latency: 833.672µs
      message: 'network-check-target-ip-10-0-140-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:47:26Z"
    - latency: 1.475956ms
      message: 'network-check-target-ip-10-0-140-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:46:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:31:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-0-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-0.ec2.internal
      uid: 01b496ec-df9b-442f-8192-dcd8b9e5d6fa
    resourceVersion: "56158"
    uid: 15cb8344-0f64-415f-84b6-8ac556ffe141
  spec:
    sourcePod: network-check-source-7d88cb55d8-fvcgl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:37:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 760.775µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:01:26Z"
    - latency: 1.667347ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:01:26Z"
    - latency: 861.113µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:00:26Z"
    - latency: 1.700375ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:00:26Z"
    - latency: 958.257µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:59:26Z"
    - latency: 1.925059ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:59:26Z"
    - latency: 868.915µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:58:26Z"
    - latency: 1.654921ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:58:26Z"
    - latency: 974.865µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:57:26Z"
    - latency: 1.709137ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:57:26Z"
kind: List
metadata:
  resourceVersion: ""