apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T17:58:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-25-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-25.ec2.internal
      uid: 6a2ba823-50cf-4452-a1d2-e44b373211ae
    resourceVersion: "37045"
    uid: 1642ad61-a0df-4ff4-829f-74248069d493
  spec:
    sourcePod: network-check-source-869dcfcdcd-6cxp6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T18:05:22Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.191466ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:19:22Z"
    - latency: 1.56106ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:18:22Z"
    - latency: 991.211µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:17:22Z"
    - latency: 1.429239ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:16:22Z"
    - latency: 1.114263ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:15:22Z"
    - latency: 1.105051ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:14:22Z"
    - latency: 1.557994ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:13:22Z"
    - latency: 963.075µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:12:22Z"
    - latency: 1.218807ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:11:22Z"
    - latency: 882.945µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:10:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T17:58:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-25-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-25.ec2.internal
      uid: 6a2ba823-50cf-4452-a1d2-e44b373211ae
    resourceVersion: "39318"
    uid: e0a4e5e7-812a-4df6-9cf5-2ab1f37176c7
  spec:
    sourcePod: network-check-source-869dcfcdcd-6cxp6
    targetEndpoint: ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T18:04:22Z"
      message: 'load-balancer-api-external: tcp connection to ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.540292ms
      message: 'load-balancer-api-external: tcp connection to ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:22:22Z"
    - latency: 8.401622ms
      message: 'load-balancer-api-external: resolved host name ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T18:22:22Z"
    - latency: 5.767698ms
      message: 'load-balancer-api-external: tcp connection to ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:21:22Z"
    - latency: 9.076998ms
      message: 'load-balancer-api-external: resolved host name ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T18:21:22Z"
    - latency: 4.705461ms
      message: 'load-balancer-api-external: tcp connection to ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:20:22Z"
    - latency: 8.478388ms
      message: 'load-balancer-api-external: resolved host name ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T18:20:22Z"
    - latency: 4.541943ms
      message: 'load-balancer-api-external: tcp connection to ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:19:22Z"
    - latency: 10.040639ms
      message: 'load-balancer-api-external: resolved host name ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T18:19:22Z"
    - latency: 5.178072ms
      message: 'load-balancer-api-external: tcp connection to ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:18:22Z"
    - latency: 8.546157ms
      message: 'load-balancer-api-external: resolved host name ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T18:18:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T17:58:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-25-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-25.ec2.internal
      uid: 6a2ba823-50cf-4452-a1d2-e44b373211ae
    resourceVersion: "39319"
    uid: 8d1eaccd-4161-43ed-be7d-655cc986ac01
  spec:
    sourcePod: network-check-source-869dcfcdcd-6cxp6
    targetEndpoint: ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T18:04:22Z"
      message: 'load-balancer-api-internal: tcp connection to ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.911718ms
      message: 'load-balancer-api-internal: tcp connection to ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:22:22Z"
    - latency: 8.374981ms
      message: 'load-balancer-api-internal: resolved host name ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T18:22:22Z"
    - latency: 5.781702ms
      message: 'load-balancer-api-internal: tcp connection to ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:21:22Z"
    - latency: 9.178918ms
      message: 'load-balancer-api-internal: resolved host name ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T18:21:22Z"
    - latency: 4.893108ms
      message: 'load-balancer-api-internal: tcp connection to ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:20:22Z"
    - latency: 8.406202ms
      message: 'load-balancer-api-internal: resolved host name ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T18:20:22Z"
    - latency: 5.05596ms
      message: 'load-balancer-api-internal: tcp connection to ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:19:22Z"
    - latency: 9.949238ms
      message: 'load-balancer-api-internal: resolved host name ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T18:19:22Z"
    - latency: 5.255102ms
      message: 'load-balancer-api-internal: tcp connection to ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:18:22Z"
    - latency: 8.582907ms
      message: 'load-balancer-api-internal: resolved host name ad2aa21e44a454045bc1d5d27ed5c043-1f5c46ba9ea10b4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T18:18:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T17:58:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-25-to-network-check-target-ip-10-0-128-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-25.ec2.internal
      uid: 6a2ba823-50cf-4452-a1d2-e44b373211ae
    resourceVersion: "37042"
    uid: 4fbad51f-e946-4116-9890-e97ef6e94c29
  spec:
    sourcePod: network-check-source-869dcfcdcd-6cxp6
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T18:05:22Z"
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.443444ms
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:19:22Z"
    - latency: 763.272µs
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:18:22Z"
    - latency: 1.531045ms
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:17:22Z"
    - latency: 1.003319ms
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:16:22Z"
    - latency: 958.046µs
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:15:22Z"
    - latency: 1.017942ms
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:14:22Z"
    - latency: 1.702287ms
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:13:22Z"
    - latency: 1.335675ms
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:12:22Z"
    - latency: 985.474µs
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:11:22Z"
    - latency: 1.514457ms
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:10:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T17:58:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-25-to-network-check-target-ip-10-0-129-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-25.ec2.internal
      uid: 6a2ba823-50cf-4452-a1d2-e44b373211ae
    resourceVersion: "37043"
    uid: 2f1ecca4-a855-42e4-9d28-de7dbf2e1ffb
  spec:
    sourcePod: network-check-source-869dcfcdcd-6cxp6
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T18:05:22Z"
      message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.395414ms
      message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:19:22Z"
    - latency: 2.320362ms
      message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:18:22Z"
    - latency: 2.444012ms
      message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:17:22Z"
    - latency: 2.55798ms
      message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:16:22Z"
    - latency: 2.412712ms
      message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:15:22Z"
    - latency: 2.433373ms
      message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:14:22Z"
    - latency: 2.326196ms
      message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:13:22Z"
    - latency: 2.293815ms
      message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:12:22Z"
    - latency: 2.446725ms
      message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:11:22Z"
    - latency: 2.195448ms
      message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:10:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T17:58:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-25-to-network-check-target-ip-10-0-131-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-25.ec2.internal
      uid: 6a2ba823-50cf-4452-a1d2-e44b373211ae
    resourceVersion: "37044"
    uid: bcf66eb5-30b1-414c-a7c9-2bdf21b2e7a9
  spec:
    sourcePod: network-check-source-869dcfcdcd-6cxp6
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T18:05:22Z"
      message: 'network-check-target-ip-10-0-131-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.762122ms
      message: 'network-check-target-ip-10-0-131-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:19:22Z"
    - latency: 2.317752ms
      message: 'network-check-target-ip-10-0-131-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:18:22Z"
    - latency: 2.17299ms
      message: 'network-check-target-ip-10-0-131-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:17:22Z"
    - latency: 2.274556ms
      message: 'network-check-target-ip-10-0-131-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:16:22Z"
    - latency: 2.265169ms
      message: 'network-check-target-ip-10-0-131-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:15:22Z"
    - latency: 2.223529ms
      message: 'network-check-target-ip-10-0-131-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:14:22Z"
    - latency: 3.089039ms
      message: 'network-check-target-ip-10-0-131-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:13:22Z"
    - latency: 2.627701ms
      message: 'network-check-target-ip-10-0-131-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:12:22Z"
    - latency: 2.094695ms
      message: 'network-check-target-ip-10-0-131-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:11:22Z"
    - latency: 2.337357ms
      message: 'network-check-target-ip-10-0-131-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:10:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T17:58:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-25-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-25.ec2.internal
      uid: 6a2ba823-50cf-4452-a1d2-e44b373211ae
    resourceVersion: "39317"
    uid: f4c0f3dc-819c-4346-aca6-2ce4fa468888
  spec:
    sourcePod: network-check-source-869dcfcdcd-6cxp6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T18:04:22Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 988.941µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:22:22Z"
    - latency: 1.847483ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T18:22:22Z"
    - latency: 871.482µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:21:22Z"
    - latency: 1.802497ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T18:21:22Z"
    - latency: 935.879µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:20:22Z"
    - latency: 1.800564ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T18:20:22Z"
    - latency: 915.053µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:19:22Z"
    - latency: 2.317422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T18:19:22Z"
    - latency: 897.326µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T18:18:22Z"
    - latency: 1.84441ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T18:18:22Z"
kind: List
metadata:
  resourceVersion: ""