kelseyhightower/kubernetes-the-hard-way

Choose this fork if Azure is the target environment and you want a step-by-step learning guide tailored to that platform. Choose upstream instead if you want the most current, cloud-agnostic tutorial with newer Kubernetes and architecture updates.

Prefer upstream unless you specifically want an older, slimmer GCP-oriented tutorial. This fork looks like a simplification rather than a maintained improvement, so it is better for narrow historical/reference use than for current learning or adoption.

Prefer this fork only if Azure-specific guidance is the priority and you are comfortable working from an older tutorial. For most adopters, the upstream repo is the safer choice because it is much more current and broader in platform support.

Choose this fork if you want a Portuguese, GCP-oriented learning guide and do not need current upstream versions or modern platform support. Choose upstream if you want the latest maintained tutorial and broader architecture coverage.

Choose this fork if you want a Talos-based hardware bootstrap path and are comfortable losing much of the original manual tutorial. Stick with upstream if you want the canonical learning-oriented hard-way walkthrough.

Prefer upstream unless you specifically need this older, GCP-framed snapshot. For most users, the fork is less attractive because it is stale and does not show concrete added functionality.

Choose this fork if your goal is a VirtualBox-first learning lab. Choose upstream if you want current Kubernetes guidance, ARM64/AMD64 support, and the latest maintained tutorial path.

Prefer this fork only if you want the GCP-centered or translated variant. For anyone starting fresh on current hardware, upstream is the better default because it is actively maintained, supports both ARM64 and AMD64, and tracks modern component versions.

Choose this fork if you want a more environment-specific, documentation-led tutorial and are comfortable working from an older baseline. Stick with upstream if you want the latest maintained versions and cross-architecture updates.