Code-first migration in high-replicated states

Hello all,

I've been working with EF Core using the Code First approach with migrations. As I move towards deploying in a Kubernetes cluster, I've encountered challenges related to handling migrations in a highly replicated environment.

### Problem

During a rolling release with multiple replicas, if one pod initiates a migration that introduces breaking changes, other pods might not be able to handle the new database schema. This can lead to inconsistencies and potential failures.

### Questions

1. How can EF Core migrations be safely managed in a rolling release scenario in Kubernetes?
2. Are there recommended patterns or practices for ensuring that all pods can handle both the old and new schema during the transition?
3. How can we prevent simultaneous migrations from multiple pods?

Any guidance or best practices in this area would be greatly appreciated. I aim to achieve zero-downtime deployments without resorting to a complete service swap.

Thank you for your assistance!