Skip to content

Latest commit

 

History

History
140 lines (71 loc) · 5.92 KB

README.md

File metadata and controls

140 lines (71 loc) · 5.92 KB
Raw

Deploy a Kubernetes cluster in GCP backed by Flux

Welcome to a highly opinionated template for deploying a single or more (gke) Kubernetes clusters with Terraform and using Flux to manage its state.

👋 Introduction

The goal of this project is to make it easy for people interested in learning Kubernetes to deploy a basic cluster at GCP and become familiar with the GitOps tool Flux.

This template implements Flux in a way that promotes legibility and ease of use for those who are new (or relatively new) to the technology and GitOps in general. It assumes a typical gke setup: namely, a single "gke prod" cluster running mostly third-party apps.

✨ Features

📝 Pre-start checklist

Before we get started everything below must be taken into consideration, you must...

  • bring a positive attitude and be ready to learn and fail a lot. The more you fail, the more you can learn from.

💻 GKE Cluster ...

TODO

🚀 Getting Started

Once you have installed Debian on your nodes, there are 6 stages to getting a Flux-managed cluster up and runnning.

🎉 Stage 1: Create a Git repository

  1. Create a new public repository by clicking the big green "Use this template" button at the top of this page.

  2. Clone your new repo to you local workstation and cd into it.

📍 All commands during the setup process are run on your local workstation within your repository directory

🌱 Stage 2: Set up your local environment

📍 Let's get the required workstation tools installed and configured.

  1. Install the most recent version of task

    📍 See the task installation docs for other platforms

TODO

  1. Install the most recent version of direnv

    📍 See the direnv installation docs for other platforms

    📍 After installing direnv be sure to hook it into your shell and after that is done run direnv allow while in your repos directory.

TODO

  1. Setup a Python virual env and install Ansible by running the following task command.

    📍 This commands requires Python 3.8+ to be installed

    # Platform agnostic
task deps

  2. Install the required tools: age, flux, cloudflared, kubectl, sops

TODO

🔧 Stage 3: Do bootstrap configuration

TODO

⚡ Stage 4: Prepare your gke configuration

TODO

⛵ Stage 5: Use Terraform to install gke

TODO

🔹 Stage 6: Install Flux in your cluster

📍 Here we will be installing flux after some quick bootstrap steps.

TODO

🎤 Verification Steps

📣 Post installation

🪝 Github Webhook

TODO

  1. Navigate to the settings of your repository on Github, under "Settings/Webhooks" press the "Add webhook" button. Fill in the webhook url and your bootstrap_flux_github_webhook_token secret and save.

🤖 Renovate

Renovate is a tool that automates dependency management. It is designed to scan your repository around the clock and open PRs for out-of-date dependencies it finds. Common dependencies it can discover are Helm charts, container images, GitHub Actions, Ansible roles... even Flux itself! Merging a PR will cause Flux to apply the update to your cluster.

To enable Renovate, click the 'Configure' button over at their Github app page and select your repository. Renovate creates a "Dependency Dashboard" as an issue in your repository, giving an overview of the status of all updates. The dashboard has interactive checkboxes that let you do things like advance scheduling or reattempt update PRs you closed without merging.

The base Renovate configuration in your repository can be viewed at .github/renovate.json5. By default it is scheduled to be active with PRs every weekend, but you can change the schedule to anything you want, or remove it if you want Renovate to open PRs right away. It is also configured to automerge some updates.

🐛 Debugging

Below is a general guide on trying to debug an issue with an resource or application. For example, if a workload/resource is not showing up or a pod has started but in a CrashLoopBackOff or Pending state.

TODO

Resolving problems that you have could take some tweaking of your YAML manifests in order to get things working, other times it could be a external factor like permissions on NFS. If you are unable to figure out your problem see the help section below.

👉 Help

  • Make a post in this repository's Github Discussions.
  • Start a thread in the support or flux-cluster-template channel in the k8s@home Discord server.

❔ What's next

The cluster is your oyster (or something like that). Below are some optional considerations you might want to review.

Ship it

To browse or get ideas on applications people are running, community member @whazor created this website as a creative way to search Flux HelmReleases across Github.

Storage

TODO

Authenticate Flux over SSH

TODO

  1. Optionally set your repository to Private in your repository settings.

🤝 Thanks

Big shout out to all the contributors, sponsors and everyone else who has helped on this project.