apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-238-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-238.ec2.internal
      uid: f6114cc2-7a68-4899-8a11-c2f1eef87d4b
    resourceVersion: "63771"
    uid: ec290b7a-ac74-4230-9aeb-a68de2bc351e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nw297
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:57:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 890.574µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:32:51Z"
    - latency: 1.046936ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:31:51Z"
    - latency: 936.397µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:30:51Z"
    - latency: 1.103241ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:29:51Z"
    - latency: 1.141742ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:28:51Z"
    - latency: 1.211243ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:27:51Z"
    - latency: 1.073924ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:26:51Z"
    - latency: 897.909µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:25:51Z"
    - latency: 1.337325ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:24:51Z"
    - latency: 1.356683ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:23:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-238-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-238.ec2.internal
      uid: f6114cc2-7a68-4899-8a11-c2f1eef87d4b
    resourceVersion: "63772"
    uid: 048d0271-23b6-4af5-bd47-83381fce3eae
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nw297
    targetEndpoint: a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:56:51Z"
      message: 'load-balancer-api-external: tcp connection to a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.672682ms
      message: 'load-balancer-api-external: tcp connection to a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:32:51Z"
    - latency: 6.476531ms
      message: 'load-balancer-api-external: resolved host name a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:32:51Z"
    - latency: 4.570148ms
      message: 'load-balancer-api-external: tcp connection to a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:31:51Z"
    - latency: 6.23967ms
      message: 'load-balancer-api-external: resolved host name a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:31:51Z"
    - latency: 4.50646ms
      message: 'load-balancer-api-external: tcp connection to a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:30:51Z"
    - latency: 6.318916ms
      message: 'load-balancer-api-external: resolved host name a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:30:51Z"
    - latency: 4.390752ms
      message: 'load-balancer-api-external: tcp connection to a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:29:51Z"
    - latency: 5.963991ms
      message: 'load-balancer-api-external: resolved host name a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:29:51Z"
    - latency: 4.374019ms
      message: 'load-balancer-api-external: tcp connection to a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:28:51Z"
    - latency: 7.461777ms
      message: 'load-balancer-api-external: resolved host name a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:28:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-238-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-238.ec2.internal
      uid: f6114cc2-7a68-4899-8a11-c2f1eef87d4b
    resourceVersion: "63773"
    uid: c4cffb7f-a8dd-4b7c-9570-c5f7e430b733
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nw297
    targetEndpoint: a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:56:51Z"
      message: 'load-balancer-api-internal: tcp connection to a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.708205ms
      message: 'load-balancer-api-internal: tcp connection to a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:32:51Z"
    - latency: 6.430011ms
      message: 'load-balancer-api-internal: resolved host name a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:32:51Z"
    - latency: 3.691021ms
      message: 'load-balancer-api-internal: tcp connection to a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:31:51Z"
    - latency: 6.159243ms
      message: 'load-balancer-api-internal: resolved host name a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:31:51Z"
    - latency: 3.895116ms
      message: 'load-balancer-api-internal: tcp connection to a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:30:51Z"
    - latency: 6.385227ms
      message: 'load-balancer-api-internal: resolved host name a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:30:51Z"
    - latency: 4.019546ms
      message: 'load-balancer-api-internal: tcp connection to a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:29:51Z"
    - latency: 6.014144ms
      message: 'load-balancer-api-internal: resolved host name a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:29:51Z"
    - latency: 4.379818ms
      message: 'load-balancer-api-internal: tcp connection to a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:28:51Z"
    - latency: 7.431807ms
      message: 'load-balancer-api-internal: resolved host name a80ce09d2953c48549485c35a6c67acc-52a00532b2887680.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:28:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-238-to-network-check-target-ip-10-0-132-151
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-238.ec2.internal
      uid: f6114cc2-7a68-4899-8a11-c2f1eef87d4b
    resourceVersion: "63769"
    uid: 2090017a-9cdb-4080-969a-44083195fe6d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nw297
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:57:51Z"
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.228984ms
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:32:51Z"
    - latency: 2.442051ms
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:31:51Z"
    - latency: 2.545407ms
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:30:51Z"
    - latency: 2.379759ms
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:29:51Z"
    - latency: 2.33654ms
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:28:51Z"
    - latency: 2.23622ms
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:27:51Z"
    - latency: 2.464859ms
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:26:51Z"
    - latency: 2.323328ms
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:25:51Z"
    - latency: 2.474114ms
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:24:51Z"
    - latency: 1.951153ms
      message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:23:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-238-to-network-check-target-ip-10-0-137-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-238.ec2.internal
      uid: f6114cc2-7a68-4899-8a11-c2f1eef87d4b
    resourceVersion: "63768"
    uid: d3bf18ee-e14d-442b-b59b-7203bcc6bd3d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nw297
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:57:51Z"
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.18414ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:32:51Z"
    - latency: 1.974845ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:31:51Z"
    - latency: 1.894136ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:30:51Z"
    - latency: 1.842999ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:29:51Z"
    - latency: 1.957731ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:28:51Z"
    - latency: 1.803453ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:27:51Z"
    - latency: 2.056468ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:26:51Z"
    - latency: 2.252482ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:25:51Z"
    - latency: 2.353535ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:24:51Z"
    - latency: 1.802429ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:23:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-238-to-network-check-target-ip-10-0-142-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-238.ec2.internal
      uid: f6114cc2-7a68-4899-8a11-c2f1eef87d4b
    resourceVersion: "63767"
    uid: 3dafa838-04d3-40c3-9e0c-de8dbdb643de
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nw297
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:57:51Z"
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 719.086µs
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:32:51Z"
    - latency: 884.995µs
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:31:51Z"
    - latency: 1.381353ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:30:51Z"
    - latency: 1.344864ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:29:51Z"
    - latency: 976.961µs
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:28:51Z"
    - latency: 798.279µs
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:27:51Z"
    - latency: 912.512µs
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:26:51Z"
    - latency: 787.119µs
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:25:51Z"
    - latency: 1.158466ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:24:51Z"
    - latency: 933.273µs
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:23:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-238-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-238.ec2.internal
      uid: f6114cc2-7a68-4899-8a11-c2f1eef87d4b
    resourceVersion: "63770"
    uid: a23bc995-7251-4992-972e-89e811683965
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nw297
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:56:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.478211ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:32:51Z"
    - latency: 1.773594ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:32:51Z"
    - latency: 1.10742ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:31:51Z"
    - latency: 1.741977ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:31:51Z"
    - latency: 928.039µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:30:51Z"
    - latency: 1.668376ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:30:51Z"
    - latency: 838.159µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:29:51Z"
    - latency: 1.745103ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:29:51Z"
    - latency: 1.053727ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:28:51Z"
    - latency: 1.852113ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:28:51Z"
kind: List
metadata:
  resourceVersion: ""