Portainer: Concurrent Stack Updates on Docker Swarm and Kubernetes Endpoints

Goal: Clarify whether Portainer applies concurrent updates to the same logical stack on a Docker Swarm endpoint and a Kubernetes endpoint as independent operations or attempts to synchronize versioning between the two platforms.

Constraints: The Portainer documentation up to version 2.19 does not specify how simultaneous stack updates are handled across orchestrator types, and the behavior may differ between the Community and Business Editions.

Questions: Does Portainer maintain separate version numbers for Swarm and Kubernetes instances of the stack, or does it try to keep them in sync? Are labels, annotations, and resource limits updated independently on each platform, risking configuration drift? Is there any built‑in locking or coordination mechanism that prevents conflicting updates?