What are the requirements for your app? Which databases, email providers, caches, queue services etc does it use? I think you will be cloud agnostic if the solu

What are the requirements for your app? Which databases, email providers, caches, queue services etc does it use? I think you will be cloud agnostic if the solutions are decoupled from any proprietary cloud APIs. If you are coupled to Dynamodb, Google Cloud Datastore or SNS you are not cloud agnostic. This is probably the minimum. What else does your solution include? Does it include hosting, infrastructure as code is it a managed service, something that clients run themselves or a SaaS? Generally if you keep deployment simple you don't have to use docker and kubernetes. For example if the app code is delivered as a monolithic .jar file or native executable and you don't have a large number of 3rd party services that need to be deployed. Docker and Kubernetes do help be cloud agnostic for a particular type of solution architecture - many microservices and potentially many other requirements like queues, caches, 3rd party including open source applications. If you had to create this distributed system on different providers it would be a lot of duplication of effort. In k8s there is still some - you most likely have to configure docker repositories, storage, load balancers, ingresses for different providers but configuration is better than reimplementation. And you still have to manage the cluster. So depending on your architecture and application requirements you may find it much simpler to use Docker and Kubernetes or them to be a needless complication. There are also certain best practices that help with portability - the 12 factor is a good guide.