A new deployment has been created and the release was successfully deployed on our AKS cluster.
We have noticed in logs that pods, for old ReplicaSet(which still exists on the cluster), are regularly executed. This is actually happening only for one specific ReplicaSet. The reason we have noticed it - it tries to perform a database update for an old db version.
Any idea why this may happen?
UPDATE: it turned out that we run "old" pod on a system test cluster (unfortunately connection string was set incorrectly :( ). The misleading thing was that ReplicaSet have the same name... because
Notice that the name of the ReplicaSet is always formatted as [DEPLOYMENT-NAME]-[RANDOM-STRING]. The random string is randomly generated and uses the pod-template-hash as a seed.