apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:23:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-147-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-147.ec2.internal
      uid: 14739a15-02cf-48ad-9cdd-50ffb76b3ca8
    resourceVersion: "54801"
    uid: 8da14bc6-ce99-43ce-a0a6-d8cf67f47c25
  spec:
    sourcePod: network-check-source-989f8b8dc-s8bk9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:30:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.037345ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:58:10Z"
    - latency: 955.405µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:57:10Z"
    - latency: 1.199587ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:56:10Z"
    - latency: 1.099916ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:55:10Z"
    - latency: 1.241171ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:54:10Z"
    - latency: 945.613µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:53:10Z"
    - latency: 960.012µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:52:10Z"
    - latency: 1.106131ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:51:10Z"
    - latency: 1.246925ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:50:10Z"
    - latency: 1.354012ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:49:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:23:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-147-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-147.ec2.internal
      uid: 14739a15-02cf-48ad-9cdd-50ffb76b3ca8
    resourceVersion: "55798"
    uid: 2c16fd36-1dc8-409b-b618-64707807ebdb
  spec:
    sourcePod: network-check-source-989f8b8dc-s8bk9
    targetEndpoint: a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:29:10Z"
      message: 'load-balancer-api-external: tcp connection to a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.804493ms
      message: 'load-balancer-api-external: tcp connection to a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:59:10Z"
    - latency: 10.012544ms
      message: 'load-balancer-api-external: resolved host name a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:59:10Z"
    - latency: 6.234696ms
      message: 'load-balancer-api-external: tcp connection to a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:58:10Z"
    - latency: 10.282263ms
      message: 'load-balancer-api-external: resolved host name a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:58:10Z"
    - latency: 5.153502ms
      message: 'load-balancer-api-external: tcp connection to a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:57:10Z"
    - latency: 8.158186ms
      message: 'load-balancer-api-external: resolved host name a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:57:10Z"
    - latency: 6.152158ms
      message: 'load-balancer-api-external: tcp connection to a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:56:10Z"
    - latency: 9.448654ms
      message: 'load-balancer-api-external: resolved host name a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:56:10Z"
    - latency: 4.938732ms
      message: 'load-balancer-api-external: tcp connection to a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:55:10Z"
    - latency: 8.726048ms
      message: 'load-balancer-api-external: resolved host name a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:55:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:23:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-147-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-147.ec2.internal
      uid: 14739a15-02cf-48ad-9cdd-50ffb76b3ca8
    resourceVersion: "55797"
    uid: 32f7a70e-a475-4bd3-b950-ffa73ead9343
  spec:
    sourcePod: network-check-source-989f8b8dc-s8bk9
    targetEndpoint: a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:29:10Z"
      message: 'load-balancer-api-internal: tcp connection to a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.849963ms
      message: 'load-balancer-api-internal: tcp connection to a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:59:10Z"
    - latency: 9.969174ms
      message: 'load-balancer-api-internal: resolved host name a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:59:10Z"
    - latency: 6.247225ms
      message: 'load-balancer-api-internal: tcp connection to a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:58:10Z"
    - latency: 10.254709ms
      message: 'load-balancer-api-internal: resolved host name a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:58:10Z"
    - latency: 5.938535ms
      message: 'load-balancer-api-internal: tcp connection to a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:57:10Z"
    - latency: 8.104872ms
      message: 'load-balancer-api-internal: resolved host name a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:57:10Z"
    - latency: 6.111481ms
      message: 'load-balancer-api-internal: tcp connection to a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:56:10Z"
    - latency: 9.504491ms
      message: 'load-balancer-api-internal: resolved host name a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:56:10Z"
    - latency: 4.915271ms
      message: 'load-balancer-api-internal: tcp connection to a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:55:10Z"
    - latency: 8.675099ms
      message: 'load-balancer-api-internal: resolved host name a94f0cf2a18664d28af9b383d1bbeccd-9d1159962823f840.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:55:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:23:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-147-to-network-check-target-ip-10-0-137-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-147.ec2.internal
      uid: 14739a15-02cf-48ad-9cdd-50ffb76b3ca8
    resourceVersion: "54800"
    uid: 13a0c4d6-c252-4e52-b4ad-af5a36c0a3f8
  spec:
    sourcePod: network-check-source-989f8b8dc-s8bk9
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:30:10Z"
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.944492ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:58:10Z"
    - latency: 1.183107ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:57:10Z"
    - latency: 1.156502ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:56:10Z"
    - latency: 1.037193ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:55:10Z"
    - latency: 905.132µs
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:54:10Z"
    - latency: 1.443181ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:53:10Z"
    - latency: 893.349µs
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:52:10Z"
    - latency: 936.569µs
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:51:10Z"
    - latency: 2.041463ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:50:10Z"
    - latency: 1.508696ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:49:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:23:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-147-to-network-check-target-ip-10-0-141-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-147.ec2.internal
      uid: 14739a15-02cf-48ad-9cdd-50ffb76b3ca8
    resourceVersion: "54799"
    uid: 2731d512-1af1-4c22-9388-5ecffa606e66
  spec:
    sourcePod: network-check-source-989f8b8dc-s8bk9
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:30:10Z"
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.531794ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:58:10Z"
    - latency: 2.213953ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:57:10Z"
    - latency: 1.963472ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:56:10Z"
    - latency: 2.20022ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:55:10Z"
    - latency: 2.39678ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:54:10Z"
    - latency: 2.466037ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:53:10Z"
    - latency: 2.070342ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:52:10Z"
    - latency: 2.131949ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:51:10Z"
    - latency: 2.470207ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:50:10Z"
    - latency: 2.436139ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:49:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:23:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-147-to-network-check-target-ip-10-0-142-114
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-147.ec2.internal
      uid: 14739a15-02cf-48ad-9cdd-50ffb76b3ca8
    resourceVersion: "54798"
    uid: c00cd15d-503c-4d04-b3e8-6725a0a7ca2a
  spec:
    sourcePod: network-check-source-989f8b8dc-s8bk9
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:30:10Z"
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.56143ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:58:10Z"
    - latency: 2.269348ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:57:10Z"
    - latency: 2.879507ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:56:10Z"
    - latency: 2.710757ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:55:10Z"
    - latency: 2.574002ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:54:10Z"
    - latency: 2.497164ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:53:10Z"
    - latency: 2.529026ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:52:10Z"
    - latency: 2.426969ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:51:10Z"
    - latency: 2.713028ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:50:10Z"
    - latency: 2.816429ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:49:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:23:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-147-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-147.ec2.internal
      uid: 14739a15-02cf-48ad-9cdd-50ffb76b3ca8
    resourceVersion: "55796"
    uid: 4e6aaefa-2abc-4bbf-a16e-4fd6e99d42be
  spec:
    sourcePod: network-check-source-989f8b8dc-s8bk9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:29:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 869.275µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:59:10Z"
    - latency: 1.7872ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:59:10Z"
    - latency: 1.130623ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:58:10Z"
    - latency: 2.553818ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:58:10Z"
    - latency: 1.13092ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:57:10Z"
    - latency: 1.852404ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:57:10Z"
    - latency: 1.085889ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:56:10Z"
    - latency: 1.943028ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:56:10Z"
    - latency: 1.337431ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:55:10Z"
    - latency: 1.812984ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:55:10Z"
kind: List
metadata:
  resourceVersion: ""