ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Migration Strategy Trade-offs A small stateless application requires a migration strategy that ensures zero downtime. Two documented Kubernetes patterns are under consideration: a RollingUpdate with maxSurge=0 and maxUnavailable=1 , or a Blue-Green deployment using separate Services and selector updates. Constraints and Uncertainties The maxSurge=0 approach
Goal Run a zero-downtime rolling update of a small application that uses EF Core Migrations, where older and newer instances temporarily share the same relational database while a pending migration changes the schema. Constraints and uncertainty EF Core does not coordinate concurrent context.Database.Migrate() calls across multiple instances, so simultaneous
A small application is being migrated with a Kubernetes Deployment using RollingUpdate. The goal is to keep the Service available during the rollout while the cluster has a fixed capacity ceiling that cannot be exceeded. With maxSurge=0 the controller must terminate an old pod before a new one can be scheduled, which respects the resource ceiling but tempora
kubernetes
entityframeworkcore
norg