<p>Have seen a super weird issue in our <strong>aws kubernetes cluster deployment</strong> where the <strong>in-memory spring cache</strong> appeared to be persistent even after a rollout restart and pod deletion. Is that even possible for an argument sake? Deletion of a pod should have deleted the container which should thereby the underlying memory.</p>
<p>Please share your thoughts, as there is no logs associated to share except the observed behavior.</p>
<p><strong>Environment Details:</strong></p>
<pre><code>Spring Boot 2.7.x
AWS EKS 1.21
Java 17
</code></pre>

Rayyan
<p>Spring Cache is an abstraction that provides automatic integration with various persistence technologies besides a simple in-memory cache.
If you have redis configured, for example, and are using spring boot, a default redis caching will take place.</p>
