Kong not support auto cache invalidation?

From this doc, we can be understood as cache invalidation must implemented by myself?


See the chunk below:

Provided you define a cache_key in your custom DAO definition, as the documentation states the entity cache will be cleared and propagated across the cluster by Kong automagically. You only need to manually handle cache evictions programmatically when you have more complex uses cases.