Comment

Comment by dvcrn

A few questions to Kubernetes people:

We are currently using Docker images locally and compose them together with docker-compose. Compose is using a custom devDockerfile identical to the normal Dockerfile, plus a self-reloading / self-compiling webserver.

For deployment we are using AWS EB and push the same Dockerfile (minus the self-reloading webserver). For heavy load applications, we use autoscaling behind a AWS loadbalancer.

Is Kubernetes giving us something over our current Docker setup? Can it improve on our workflow?

Is the time investment for learning this worth it for private projects vs plain Docker that can get pushed to Heroku / Google / AWS?

I have Kubernetes on my list of things I want to check out but every time I go into the getting started guides for local environments, it seems like a lot of work for just setting the environment up. One of the things I love Docker is that I can write the Dockerfile and everyone from our team can very easily use it and immediately has the app running. No Docker? Just install Docker and compose through brew or download it from the website. That's it.

parent dvcrn 10 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton