ama VS kubernetes-the-hard-way

If you want to stick on one machine, you can always just use a single node Docker Swarm to get the fully automated zero downtime deploys you want with Docker Compose:

https://github.com/BretFisher/ama/discussions/146

Follow Bret here

Check out Bret Fishers courses and content - https://www.bretfisher.com/

This Awesome List is maintained by Bret Fisher (and coming soon, maintainers #3). This is a curated list of working tools and resources for using Swarm. It is not an official list, but a community effort to help people find the best tools and resources for Swarm in 2023 and beyond.

https://www.bretfisher.com/ - awesome guy, awesome discord (https://devops.fan). Awesome Talks

Composer is not meant to run in production. It is only meant for development or building images. Make sure to read Getting started with swarm mode and check this if you want to use run your build image on a proper environment. (recommended)

I don't know if I would call myself an expert, but worrying about security is a big concern of mine and my job. While there are some security benefits to running your app in a container, you're correct in thinking there are some things to keep in mind while writing your Dockerfiles and using Docker. Check out Bret Fisher's write up on security concerns using Docker. This is the second time that I've mentioned him. He's a Docker Captain and recognized by Docker as an expert. His advice is sound.

Only one host for production environment. What to use: docker-compose or single node swarm? · Issue #8 · BretFisher/ama (github.com)

As I delved into the world of Kubernetes, I opted for what seemed like the scenic route—until reality hit. With determination and a sprinkle of naivety, I plunged into crafting a Kubernetes cluster from scratch. Little did I know, I was in for a wild ride of commands, configurations, and complexities. But fear not! With the guiding light of a course based on the notorious "Kubernetes The Hard Way" GitHub repository, albeit customized for AWS instead of Google Cloud, I embarked on my journey to build my digital fortress, one step at a time.

Another resource that I found pretty helpful was "Kubernetes the Hard Way" by Kelsey Hightower despite its complexity.

https://github.com/kelseyhightower/kubernetes-the-hard-way

I recently published Kubernetes the Harder Way, a guide loosely based on Kelsey Hightower's Kubernetes the Hard Way, but lenghtier, more explanatory, broader in scope, and - most importantly - harder, by targeting a local machine instead of Google Cloud Platform.

How about this? It will setup a kubernetes cluster on GCP with 3 worker nodes?

https://github.com/kelseyhightower/kubernetes-the-hard-way

Some costs here but click on the google cloud calc as it seems to have gone up since he wrote this:

If you wanna go all in: https://github.com/kelseyhightower/kubernetes-the-hard-way

Oh, and both: "Kubernetes up and Running" and "Production Kubernetes" are great books.

Using Kubernetes The Hard Way is a great way to learn it deeply and quickly.

If you wanna learn it deeply and quickly, Kelsey Hightower's Kubernetes the hard way is fantastic!