Broader questions include: what will be the long-term effect on user-perceived quality of releases [43, 45], how quickly will technical debt ramp up when release cycles are so short and can end users keep up with a continuous stream of new releases?
Consider a single Kubernetes cluster running on a particular version in a production environment with live request traffic. For every new release, a new version is deployed. During a release, a release engineer might expect a certain delay or downtime due to the merge conflicts, incorrect package dependency resolution, etc. That is what I understood when the author says increased technical debt.
Such technical debts can be minimized by using high availability cluster setups to divert the traffic. DNS providers like NS2, Cloudflare, and Amazon Route 53 have a way of health checking your applications. We can configure the DNS providers with a failover i.e. if one cluster fails to respond to the