Questions about the termination state of WASM filter plugins: do they exist?

[anto-progetica]

Hi, I'm developing a WASM filter for Kong Gateway running in a Kubernetes cluster. Everything works correctly, but I'm experiencing an unexpected state behavior and I'm not sure if it's a bug or an architectural aspect of the system.

In practice, when I change the plugin configuration, I notice that instances with the old configuration continue to run even though they aren't actually functioning (the new configurations work properly for accessing clients with new instance). Thanks to an on_tick function that performs logging, I can see that previous configurations are being printed in the logs alongside the newly inserted one (simultaneously).

I want to emphasize that the latest configuration is the one that's actually correctly active for handling client requests, but for some reason the old instances persist in the background.

Kong 3.9.1
wasm filter: Language: Rust, crate proxy-wasm 0.2.3