apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T13:20:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-235-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-235.ec2.internal
      uid: c4004598-5d53-4a3d-a697-8cbd861191dd
    resourceVersion: "62895"
    uid: 31136572-376e-4362-8220-0b12cc82e64c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tvdgj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T13:27:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 752.925µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:02:37Z"
    - latency: 1.141122ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:01:37Z"
    - latency: 839.2µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:00:37Z"
    - latency: 1.367562ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:59:37Z"
    - latency: 1.048996ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:58:37Z"
    - latency: 1.026089ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:57:37Z"
    - latency: 1.563365ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:56:37Z"
    - latency: 901.028µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:55:37Z"
    - latency: 884.975µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:54:37Z"
    - latency: 785.205µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:53:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T13:20:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-235-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-235.ec2.internal
      uid: c4004598-5d53-4a3d-a697-8cbd861191dd
    resourceVersion: "62897"
    uid: 8748bbc3-0a61-4780-bc45-f647917ac430
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tvdgj
    targetEndpoint: a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T13:26:37Z"
      message: 'load-balancer-api-external: tcp connection to a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.609825ms
      message: 'load-balancer-api-external: tcp connection to a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:02:37Z"
    - latency: 8.038576ms
      message: 'load-balancer-api-external: resolved host name a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:02:37Z"
    - latency: 4.526924ms
      message: 'load-balancer-api-external: tcp connection to a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:01:37Z"
    - latency: 9.044172ms
      message: 'load-balancer-api-external: resolved host name a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:01:37Z"
    - latency: 5.784906ms
      message: 'load-balancer-api-external: tcp connection to a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:00:37Z"
    - latency: 8.450273ms
      message: 'load-balancer-api-external: resolved host name a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:00:37Z"
    - latency: 4.248743ms
      message: 'load-balancer-api-external: tcp connection to a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:59:37Z"
    - latency: 8.359619ms
      message: 'load-balancer-api-external: resolved host name a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:59:37Z"
    - latency: 3.762074ms
      message: 'load-balancer-api-external: tcp connection to a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:58:37Z"
    - latency: 8.937527ms
      message: 'load-balancer-api-external: resolved host name a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:58:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T13:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-235-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-235.ec2.internal
      uid: c4004598-5d53-4a3d-a697-8cbd861191dd
    resourceVersion: "62896"
    uid: ce567250-5c4a-4369-a432-009538b55c23
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tvdgj
    targetEndpoint: a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T13:26:37Z"
      message: 'load-balancer-api-internal: tcp connection to a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.037014ms
      message: 'load-balancer-api-internal: tcp connection to a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:02:37Z"
    - latency: 8.119404ms
      message: 'load-balancer-api-internal: resolved host name a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:02:37Z"
    - latency: 3.79312ms
      message: 'load-balancer-api-internal: tcp connection to a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:01:37Z"
    - latency: 9.110539ms
      message: 'load-balancer-api-internal: resolved host name a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:01:37Z"
    - latency: 5.771025ms
      message: 'load-balancer-api-internal: tcp connection to a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:00:37Z"
    - latency: 8.532923ms
      message: 'load-balancer-api-internal: resolved host name a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:00:37Z"
    - latency: 3.607028ms
      message: 'load-balancer-api-internal: tcp connection to a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:59:37Z"
    - latency: 8.304402ms
      message: 'load-balancer-api-internal: resolved host name a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:59:37Z"
    - latency: 4.928547ms
      message: 'load-balancer-api-internal: tcp connection to a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:58:37Z"
    - latency: 9.033379ms
      message: 'load-balancer-api-internal: resolved host name a1cd3d89dca1d4a0d98d25f6451e2746-07857199f9402a01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:58:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T13:20:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-235-to-network-check-target-ip-10-0-130-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-235.ec2.internal
      uid: c4004598-5d53-4a3d-a697-8cbd861191dd
    resourceVersion: "62892"
    uid: 30a0563d-3bc2-4477-b571-e0474859fba5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tvdgj
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T13:27:37Z"
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.355496ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:02:37Z"
    - latency: 2.359577ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:01:37Z"
    - latency: 2.614426ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:00:37Z"
    - latency: 2.201123ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:59:37Z"
    - latency: 2.248511ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:58:37Z"
    - latency: 2.223006ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:57:37Z"
    - latency: 2.234573ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:56:37Z"
    - latency: 2.39002ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:55:37Z"
    - latency: 2.185817ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:54:37Z"
    - latency: 2.132183ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:53:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T13:20:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-235-to-network-check-target-ip-10-0-136-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-235.ec2.internal
      uid: c4004598-5d53-4a3d-a697-8cbd861191dd
    resourceVersion: "62893"
    uid: 0369a544-60f0-4b5f-a955-b1e437955667
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tvdgj
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T13:27:37Z"
      message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.238733ms
      message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:02:37Z"
    - latency: 2.364357ms
      message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:01:37Z"
    - latency: 2.55198ms
      message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:00:37Z"
    - latency: 2.439601ms
      message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:59:37Z"
    - latency: 2.229899ms
      message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:58:37Z"
    - latency: 2.274902ms
      message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:57:37Z"
    - latency: 2.004386ms
      message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:56:37Z"
    - latency: 2.365931ms
      message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:55:37Z"
    - latency: 2.955668ms
      message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:54:37Z"
    - latency: 2.039784ms
      message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:53:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T13:20:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-235-to-network-check-target-ip-10-0-141-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-235.ec2.internal
      uid: c4004598-5d53-4a3d-a697-8cbd861191dd
    resourceVersion: "62891"
    uid: faea48a3-b26f-47ab-bcb9-8f1e6c383d58
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tvdgj
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T13:27:37Z"
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.260549ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:02:37Z"
    - latency: 1.409352ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:01:37Z"
    - latency: 842.79µs
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:00:37Z"
    - latency: 896.107µs
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:59:37Z"
    - latency: 1.006769ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:58:37Z"
    - latency: 1.23441ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:57:37Z"
    - latency: 721.66µs
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:56:37Z"
    - latency: 1.349968ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:55:37Z"
    - latency: 1.094531ms
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:54:37Z"
    - latency: 782.293µs
      message: 'network-check-target-ip-10-0-141-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:53:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T13:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-235-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-235.ec2.internal
      uid: c4004598-5d53-4a3d-a697-8cbd861191dd
    resourceVersion: "62894"
    uid: 4c644d70-add3-4242-a6b6-658530978557
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tvdgj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T13:26:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.014517ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:02:37Z"
    - latency: 1.709221ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:02:37Z"
    - latency: 1.305852ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:01:37Z"
    - latency: 1.938298ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:01:37Z"
    - latency: 833.272µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T14:00:37Z"
    - latency: 1.82753ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T14:00:37Z"
    - latency: 890.51µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:59:37Z"
    - latency: 1.847701ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:59:37Z"
    - latency: 1.006488ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:58:37Z"
    - latency: 1.695457ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:58:37Z"
kind: List
metadata:
  resourceVersion: ""