Hi :), I did give mention to putting it all in one file in Kubernetes > You can define everything in one file in Kubernetes but it won't do much for readabilit

Hi :), I did give mention to putting it all in one file in Kubernetes > You can define everything in one file in Kubernetes but it won't do much for readability. My emphasis was on how much less config I have to go through to grasp the details of my setup in entirety given a single dense kubernetes config file vs a single compose file. You mention using kubectl apply to deploy >Also, don't use "kubectl create" — use "kubectl apply". It will create or update as needed. It even supports recursing through directories. It is indeed better than kubectl create, however I would point out that if you use it with the intention of running it recursively within a directory, you will have little control over the order of creation of resources, and you will run into errors if one of your resources depends on another resource which has not been created yet. Before I continue :) you believe that I am using Kubernetes in the most complicated way possible and thus making it seem harder to use than it actually is, however I'd point out that I was porting a "production" cluster to Swarm, and for deployment on dedicated machines and not a generic cloud provider. I therefore had been using whatever advanced options I had at my disposal to make my setup as robust as possible.