Hello 
Sadly we face an issue right now with the worker versioning garbage collection.
From the docs:
when you deploy your 101st Worker Version in a Worker Deployment, the server looks at the oldest drained version in the Worker deployment. If it has had no pollers in the last 5 minutes, the server deletes it
( Worker Versioning | Temporal Platform Documentation )
We are exactly in this situation. But instead of the expected behavior we now get bombarded with this error on the matching pod:
cannot add version #### since maximum number of versions (100) have been registered in the deployment
There are plenty of drained versions. These worker pods were also already deleted by the controller like expected.
Besides this issue we have no other so far with versioning or the worker controller.
Version deployed in K8n is: 1.29.1
Is this a bug? One that’s maybe solved in newer versions already? I’m already reading through patch notes and even commits to find something, but failed so far.
Have we just configured something wrong? A hint would be nice.
Best,
Sophie