apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T03:50:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-61-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-61.ec2.internal
      uid: b70690f2-6477-4fb1-bef8-a659add1e0b1
    resourceVersion: "47907"
    uid: 9d1225ed-4542-4ec5-af66-c5813ed8efb4
  spec:
    sourcePod: network-check-source-dbd9cf844-wbkt2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T03:57:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.025676ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:18:49Z"
    - latency: 1.526054ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:17:49Z"
    - latency: 923.7µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:16:49Z"
    - latency: 942.289µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:15:49Z"
    - latency: 1.273132ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:14:49Z"
    - latency: 942.358µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:13:49Z"
    - latency: 1.173967ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:12:49Z"
    - latency: 963.182µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:11:49Z"
    - latency: 1.059703ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:10:49Z"
    - latency: 938.764µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:09:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T03:50:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-61-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-61.ec2.internal
      uid: b70690f2-6477-4fb1-bef8-a659add1e0b1
    resourceVersion: "50064"
    uid: 6091267f-6087-418c-8255-8052de89e180
  spec:
    sourcePod: network-check-source-dbd9cf844-wbkt2
    targetEndpoint: aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T03:56:49Z"
      message: 'load-balancer-api-external: tcp connection to aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.611158ms
      message: 'load-balancer-api-external: tcp connection to aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:20:49Z"
    - latency: 9.15396ms
      message: 'load-balancer-api-external: resolved host name aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T04:20:49Z"
    - latency: 4.028483ms
      message: 'load-balancer-api-external: tcp connection to aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:19:49Z"
    - latency: 8.513293ms
      message: 'load-balancer-api-external: resolved host name aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T04:19:49Z"
    - latency: 5.29087ms
      message: 'load-balancer-api-external: tcp connection to aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:18:49Z"
    - latency: 9.040905ms
      message: 'load-balancer-api-external: resolved host name aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T04:18:49Z"
    - latency: 4.561643ms
      message: 'load-balancer-api-external: tcp connection to aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:17:49Z"
    - latency: 9.074823ms
      message: 'load-balancer-api-external: resolved host name aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T04:17:49Z"
    - latency: 5.27473ms
      message: 'load-balancer-api-external: tcp connection to aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:16:49Z"
    - latency: 9.535087ms
      message: 'load-balancer-api-external: resolved host name aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T04:16:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T03:50:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-61-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-61.ec2.internal
      uid: b70690f2-6477-4fb1-bef8-a659add1e0b1
    resourceVersion: "50065"
    uid: c94960df-ec62-4922-b6c2-4d04423c7210
  spec:
    sourcePod: network-check-source-dbd9cf844-wbkt2
    targetEndpoint: aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T03:56:49Z"
      message: 'load-balancer-api-internal: tcp connection to aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.745774ms
      message: 'load-balancer-api-internal: tcp connection to aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:20:49Z"
    - latency: 9.102011ms
      message: 'load-balancer-api-internal: resolved host name aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T04:20:49Z"
    - latency: 4.841144ms
      message: 'load-balancer-api-internal: tcp connection to aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:19:49Z"
    - latency: 8.405305ms
      message: 'load-balancer-api-internal: resolved host name aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T04:19:49Z"
    - latency: 5.285707ms
      message: 'load-balancer-api-internal: tcp connection to aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:18:49Z"
    - latency: 8.946691ms
      message: 'load-balancer-api-internal: resolved host name aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T04:18:49Z"
    - latency: 4.558299ms
      message: 'load-balancer-api-internal: tcp connection to aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:17:49Z"
    - latency: 9.134829ms
      message: 'load-balancer-api-internal: resolved host name aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T04:17:49Z"
    - latency: 5.259625ms
      message: 'load-balancer-api-internal: tcp connection to aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:16:49Z"
    - latency: 9.583071ms
      message: 'load-balancer-api-internal: resolved host name aa42bda055ae1422f93d8ae0a985e443-a77d6394005163e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T04:16:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T03:50:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-61-to-network-check-target-ip-10-0-132-53
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-61.ec2.internal
      uid: b70690f2-6477-4fb1-bef8-a659add1e0b1
    resourceVersion: "47905"
    uid: 85c4b7bc-eabc-4707-8d8f-ea666a1608b8
  spec:
    sourcePod: network-check-source-dbd9cf844-wbkt2
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T03:57:49Z"
      message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.296458ms
      message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:18:49Z"
    - latency: 2.824942ms
      message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:17:49Z"
    - latency: 2.426834ms
      message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:16:49Z"
    - latency: 2.513754ms
      message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:15:49Z"
    - latency: 2.395226ms
      message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:14:49Z"
    - latency: 2.271391ms
      message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:13:49Z"
    - latency: 2.597069ms
      message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:12:49Z"
    - latency: 2.511327ms
      message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:11:49Z"
    - latency: 2.194522ms
      message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:10:49Z"
    - latency: 2.477611ms
      message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:09:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T03:50:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-61-to-network-check-target-ip-10-0-139-39
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-61.ec2.internal
      uid: b70690f2-6477-4fb1-bef8-a659add1e0b1
    resourceVersion: "47904"
    uid: 87d7eefe-28d7-412b-9da6-b2f7cc0caf18
  spec:
    sourcePod: network-check-source-dbd9cf844-wbkt2
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T03:57:49Z"
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.249246ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:18:49Z"
    - latency: 2.162714ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:17:49Z"
    - latency: 2.450732ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:16:49Z"
    - latency: 2.366315ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:15:49Z"
    - latency: 2.392253ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:14:49Z"
    - latency: 2.4906ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:13:49Z"
    - latency: 2.435375ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:12:49Z"
    - latency: 2.599805ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:11:49Z"
    - latency: 2.316592ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:10:49Z"
    - latency: 2.77539ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:09:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T03:50:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-61-to-network-check-target-ip-10-0-139-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-61.ec2.internal
      uid: b70690f2-6477-4fb1-bef8-a659add1e0b1
    resourceVersion: "47903"
    uid: 376b714d-4650-4162-9adb-147bbe2381e8
  spec:
    sourcePod: network-check-source-dbd9cf844-wbkt2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T03:57:49Z"
      message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.32849ms
      message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:18:49Z"
    - latency: 826.67µs
      message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:17:49Z"
    - latency: 867.043µs
      message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:16:49Z"
    - latency: 944.701µs
      message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:15:49Z"
    - latency: 760.652µs
      message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:14:49Z"
    - latency: 974.842µs
      message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:13:49Z"
    - latency: 861.419µs
      message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:12:49Z"
    - latency: 1.017432ms
      message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:11:49Z"
    - latency: 1.424572ms
      message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:10:49Z"
    - latency: 899.588µs
      message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:09:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T03:50:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-61-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-61.ec2.internal
      uid: b70690f2-6477-4fb1-bef8-a659add1e0b1
    resourceVersion: "50062"
    uid: dc05d882-ddc9-4566-9a62-6c4c8431f493
  spec:
    sourcePod: network-check-source-dbd9cf844-wbkt2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T03:56:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 812.347µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:20:49Z"
    - latency: 1.637329ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T04:20:49Z"
    - latency: 906.252µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:19:49Z"
    - latency: 1.638145ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T04:19:49Z"
    - latency: 899.682µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:18:49Z"
    - latency: 1.565994ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T04:18:49Z"
    - latency: 824.359µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:17:49Z"
    - latency: 2.100644ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T04:17:49Z"
    - latency: 886.816µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T04:16:49Z"
    - latency: 1.911895ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T04:16:49Z"
kind: List
metadata:
  resourceVersion: ""