apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:01:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-0-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-0.ec2.internal
      uid: 39e9b646-91e2-47a3-90ee-644be283be07
    resourceVersion: "76570"
    uid: e6527a19-9882-4cb0-93e3-068350b76ebd
  spec:
    sourcePod: network-check-source-7cbc45fddc-l26bh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:08:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.638948ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:04:52Z"
    - latency: 1.477972ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:03:52Z"
    - latency: 1.042974ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:02:52Z"
    - latency: 810.533µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:01:52Z"
    - latency: 1.032701ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:00:52Z"
    - latency: 1.109726ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:59:52Z"
    - latency: 1.143535ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:58:52Z"
    - latency: 943.279µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:57:52Z"
    - latency: 1.487037ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:56:52Z"
    - latency: 1.300477ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:55:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:01:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-0-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-0.ec2.internal
      uid: 39e9b646-91e2-47a3-90ee-644be283be07
    resourceVersion: "73356"
    uid: d4e7299e-1b65-4246-9af3-fd079baa577c
  spec:
    sourcePod: network-check-source-7cbc45fddc-l26bh
    targetEndpoint: a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:07:52Z"
      message: 'load-balancer-api-external: tcp connection to a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.852255ms
      message: 'load-balancer-api-external: tcp connection to a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:01:52Z"
    - latency: 8.156452ms
      message: 'load-balancer-api-external: resolved host name a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:01:52Z"
    - latency: 3.89453ms
      message: 'load-balancer-api-external: tcp connection to a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:00:52Z"
    - latency: 6.512312ms
      message: 'load-balancer-api-external: resolved host name a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:00:52Z"
    - latency: 3.623555ms
      message: 'load-balancer-api-external: tcp connection to a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:59:52Z"
    - latency: 11.738465ms
      message: 'load-balancer-api-external: resolved host name a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:59:52Z"
    - latency: 4.090079ms
      message: 'load-balancer-api-external: tcp connection to a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:58:52Z"
    - latency: 6.345705ms
      message: 'load-balancer-api-external: resolved host name a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:58:52Z"
    - latency: 4.703656ms
      message: 'load-balancer-api-external: tcp connection to a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:57:52Z"
    - latency: 9.603166ms
      message: 'load-balancer-api-external: resolved host name a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:57:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:01:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-0-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-0.ec2.internal
      uid: 39e9b646-91e2-47a3-90ee-644be283be07
    resourceVersion: "73357"
    uid: 23286b92-f6f1-4906-b978-b0380a2f4317
  spec:
    sourcePod: network-check-source-7cbc45fddc-l26bh
    targetEndpoint: a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:07:52Z"
      message: 'load-balancer-api-internal: tcp connection to a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.838902ms
      message: 'load-balancer-api-internal: tcp connection to a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:01:52Z"
    - latency: 8.148248ms
      message: 'load-balancer-api-internal: resolved host name a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:01:52Z"
    - latency: 4.059449ms
      message: 'load-balancer-api-internal: tcp connection to a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:00:52Z"
    - latency: 6.473971ms
      message: 'load-balancer-api-internal: resolved host name a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:00:52Z"
    - latency: 3.671676ms
      message: 'load-balancer-api-internal: tcp connection to a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:59:52Z"
    - latency: 11.521896ms
      message: 'load-balancer-api-internal: resolved host name a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:59:52Z"
    - latency: 4.114518ms
      message: 'load-balancer-api-internal: tcp connection to a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:58:52Z"
    - latency: 6.360506ms
      message: 'load-balancer-api-internal: resolved host name a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:58:52Z"
    - latency: 4.704303ms
      message: 'load-balancer-api-internal: tcp connection to a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:57:52Z"
    - latency: 9.627631ms
      message: 'load-balancer-api-internal: resolved host name a14e84aea5c0a4359bb34a5262a07896-0112c3c7058c7ff7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:57:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:01:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-0-to-network-check-target-ip-10-0-130-251
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-0.ec2.internal
      uid: 39e9b646-91e2-47a3-90ee-644be283be07
    resourceVersion: "76568"
    uid: d37de213-f465-45ea-a12d-013742bb35a7
  spec:
    sourcePod: network-check-source-7cbc45fddc-l26bh
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:08:52Z"
      message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.664817ms
      message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:04:52Z"
    - latency: 2.244874ms
      message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:03:52Z"
    - latency: 2.110562ms
      message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:02:52Z"
    - latency: 2.144741ms
      message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:01:52Z"
    - latency: 2.219302ms
      message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:00:52Z"
    - latency: 2.396308ms
      message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:59:52Z"
    - latency: 1.990583ms
      message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:58:52Z"
    - latency: 2.36207ms
      message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:57:52Z"
    - latency: 2.652154ms
      message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:56:52Z"
    - latency: 2.120073ms
      message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:55:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:01:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-0-to-network-check-target-ip-10-0-130-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-0.ec2.internal
      uid: 39e9b646-91e2-47a3-90ee-644be283be07
    resourceVersion: "76569"
    uid: 242ebb9a-42d4-4d85-8a61-b5464a6beb66
  spec:
    sourcePod: network-check-source-7cbc45fddc-l26bh
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:08:52Z"
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.351656ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:04:52Z"
    - latency: 2.003761ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:03:52Z"
    - latency: 2.237318ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:02:52Z"
    - latency: 2.354642ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:01:52Z"
    - latency: 2.582792ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:00:52Z"
    - latency: 2.399892ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:59:52Z"
    - latency: 2.505071ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:58:52Z"
    - latency: 2.626164ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:57:52Z"
    - latency: 2.529775ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:56:52Z"
    - latency: 2.365238ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:55:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:01:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-0-to-network-check-target-ip-10-0-132-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-0.ec2.internal
      uid: 39e9b646-91e2-47a3-90ee-644be283be07
    resourceVersion: "76567"
    uid: 796bb291-c9f6-4e4d-87ca-cccda0019ba6
  spec:
    sourcePod: network-check-source-7cbc45fddc-l26bh
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:08:52Z"
      message: 'network-check-target-ip-10-0-132-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.187471ms
      message: 'network-check-target-ip-10-0-132-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:04:52Z"
    - latency: 958.591µs
      message: 'network-check-target-ip-10-0-132-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:03:52Z"
    - latency: 1.595385ms
      message: 'network-check-target-ip-10-0-132-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:02:52Z"
    - latency: 855.672µs
      message: 'network-check-target-ip-10-0-132-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:01:52Z"
    - latency: 895.697µs
      message: 'network-check-target-ip-10-0-132-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:00:52Z"
    - latency: 1.22935ms
      message: 'network-check-target-ip-10-0-132-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:59:52Z"
    - latency: 1.318167ms
      message: 'network-check-target-ip-10-0-132-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:58:52Z"
    - latency: 1.112547ms
      message: 'network-check-target-ip-10-0-132-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:57:52Z"
    - latency: 1.163873ms
      message: 'network-check-target-ip-10-0-132-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:56:52Z"
    - latency: 1.450486ms
      message: 'network-check-target-ip-10-0-132-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:55:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:01:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-0-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-0.ec2.internal
      uid: 39e9b646-91e2-47a3-90ee-644be283be07
    resourceVersion: "73350"
    uid: 9fba3475-9680-4726-b40a-80316e13cdfb
  spec:
    sourcePod: network-check-source-7cbc45fddc-l26bh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:07:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 879.717µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:01:52Z"
    - latency: 1.799205ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:01:52Z"
    - latency: 958.513µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:00:52Z"
    - latency: 1.988185ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:00:52Z"
    - latency: 1.160841ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:59:52Z"
    - latency: 1.686642ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:59:52Z"
    - latency: 1.103471ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:58:52Z"
    - latency: 1.886599ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:58:52Z"
    - latency: 987.242µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:57:52Z"
    - latency: 1.95954ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:57:52Z"
kind: List
metadata:
  resourceVersion: ""