I'm hoping these kinds of policies continue to be phased out. The Kubernetes world has changed a lot in the past few years in ways that make databases-in-k8s m

I'm hoping these kinds of policies continue to be phased out. The Kubernetes world has changed a lot in the past few years in ways that make databases-in-k8s more appealing. Such as: - Kubernetes "eating the world", meaning some teams may not even have good options for databases outside k8s (particularly onprem). - Infrastructure-as-code being more prevalent. Since you already have to use k8s manifests for the rest of your app, adding another IaC tool to set up RDS may be undesirable. - The rise of microservices, where companies may have hundreds of services that need their own separate data stores (many which don't see high enough traffic to justify the cost of a managed database service). - Excellent options like the bitnami helm charts: https://github.com/bitnami/charts https://github.com/bitnami/charts or apparently Vitess (haven't used it myself): https://vitess.io/ https://vitess.io/ Obviously if the use-case is a few huge, highly-tuned, super-critical databases, managed database services are perfect for that. But IMO a blanket ban might be restricting adoption of some more modern development practices.