kubernetes-the-hard-way VS kops

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!

The general problem of patching resource definitions that are not fully under your control has also been recognized for some time. This is true of default resources created and updated by cluster maintenance tools (e.g. kOps), or by public helm charts that you use to install common services and operators (e.g. nginx-ingress, cert-manager, and so on). High quality charts will allow you to override the configuration of important components such as service account references, but some simpler charts offer much less configuration.

The kops documentation is not very clear about this.

Very fast progress and great article with lots of useful information. I found myself nodding a lot having recently seen GitLab Dedicated https://docs.gitlab.com/ee/subscriptions/gitlab_dedicated/ being developed that had my similar challenges. I wonder what other people think of Kops https://kops.sigs.k8s.io/

note: I work with kube on a daily basis. All current clusters under my care use a managed backplane service though there are a number of small (3+ years-old) clusters that I still keep an eye on that were initialized using kops.

kOps with your own instances.

Companies run their own clusters (sometimes for cost reasons), using tools like kops, and kubeadm to set up their own clusters.

curl -Lo kops https://github.com/kubernetes/kops/releases/download/$(curl -s https://api.github.com/repos/kubernetes/kops/releases/latest | grep tag_name | cut -d '"' -f 4)/kops-linux-amd64 chmod +x kops sudo mv kops /usr/local/bin/

Kops is a cluster setup and management command line tool that deploys a Kubernetes cluster to AWS. It provides configuration abstractions such as manifest YAML files that facilitate node and components configuration. And like Ansible, it will provide dry-run capabilities and ensures idempotency of changing the nodes.