Braunson

@matt-royal the point of this issue was I believe this should be the default. This is a 5 cluster deployment and it is expected it should be highly available without...

I thought the deployment was targeted close to something HA with the exception of the DB and Blobstore. If the goal is to be similar to cf-deployment on Bosh then...

The same could be said about the logging capabilities of cf-for-k8s. It would be nice to have the ability to ship them to another stack like ELK. I think I...

I think your second point is mostly true. However, there are a few instances were apps would still go offline even with 2+ instances. 1. Imagine I have a 5...

No problem @Birdrock I actually just made a small edit which might be relevant to your investigating with Eirini. > cf-for-k8s specifically makes this downtime more likely because it uses...

> Could we solve this without exposing PDBs to the end-user? 50% could work but it makes assumptions about the load that an app can handle. I would prefer it...

@loewenstein Hmm I'm confused by your reply. It makes perfect sense what you said but that's exactly why I was thinking it's better being an individual app setting vs foundational....

@loewenstein Ah yea still I don't think that would be preferred. For instance I might have an app with two instances but still not really worry about downtime (perhaps it's...

At least one instance could cause issues under load. Or are we discussing having a PDB with minAvailable = instances-1? Thus, minimizing the amount of app disruption

@herrjulz @bkrannich I agree that a default behaviour that matches Diego would be good, but I don't think that we should stop there. As @herrjulz said I would like to...