The document at Best Practices when using decK - v1.19.x | Kong Docs states:
"Always ensure that you have only one decK process running at any time. Multiple processes can conflict with each other and potentially corrupt Kong's configuration."
But is it still true when we use Distributed Configurations with tags that ensure updates occur in different resources of Kong?
Hi @Danilo_Rosa ,
I think the intend of saying not to use multiple deck is straight-forward and wants to avoid conflicts such as if you have multiple deck running and taking deck dump at different locations at different times, it will surely create inconsistent configurations and conflicts.
Regarding DS with tags, of course, we can use deck with tags that will ensure only intended configuration is updated. Now, it does not matter how many decks you have.