# Caching of k8s objects in Lens

**URL:** https://forums.k8slens.dev/t/caching-of-k8s-objects-in-lens/671
**Category:** Lens Support & Troubleshooting
**Tags:** lens-desktop, kubernetes, cluster
**Created:** [July 14, 2023, 8:32am UTC](https://forums.k8slens.dev/t/caching-of-k8s-objects-in-lens/671 "2023-07-14T08:32:30Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![agmimidi](https://forums.k8slens.dev/letter_avatar_proxy/v4/letter/a/8edcca/32.png) [@agmimidi](https://forums.k8slens.dev/u/agmimidi)
#### Post date: [July 14, 2023, 8:32am UTC](https://forums.k8slens.dev/t/caching-of-k8s-objects-in-lens/671/1 "2023-07-14T08:32:30Z")

</div>

Hi all,  
We have an audit policy in our cluster to audit access to specific k8s objects.  
We have noticed that while for example accessing (verb GET) an object via kubectl, there is a corresponding real-time audit trail. The same does not hold when we access the same object via the Lens UI.  
Does Lens pre-load and cache objects in the background and if so is there a way to control this behavior?