Introduction to GitOps - Flux Based

If you work with Kubernetes, then GitOps is going to make your world a better place by enabling you to perform automated zero effort deployments into Kubernetes - as many times as you require per day!

This introductory level training lesson is designed to bring you quickly up to speed with the basic features and processes involved in a GitOps workflow. This lesson will present to you the key features and GitOps workflow theory. 

GitOps defines a better approach to performing Continuous Delivery in the context of a Kubernetes cluster. It does so by promoting Git as the single source of truth for declarative infrastructure and workloads.

If you have thoughts or suggestions regarding this content, please contact us at platformsupport@qa.com.

Learning Objectives

By completing this lesson, you will:

• Learn about the principles, practices, and processes that drive a GitOps workflow
• Learn how to establish GitOps to automate and synchronize cluster state with Git repos
• Learn how GitOps uses Git as its single source of truth
• Learn and understand how to configure and enable a GitOps workflow using tools such as Helm, Tiller, and Flux

Intended Audience

This lesson is intended for:

• Anyone interested in learning GitOps
• Software Developers interested in the GitOps workflow
• DevOps practitioners looking to learn how to setup, manage and maintain applications using a GitOps workflow

Prerequisites

To get the most from this lesson, you should have at least:

• A basic understanding of containers and containerisation
• A basic understanding of Kubernetes - and container orchestration and scheduling
• A basic understanding of software development and the software development life cycle
• A basic understanding of Git and Git repositories
  

Source Code

The sample GitOps project code as used within the demonstrations is located here:

https://github.com/cloudacademy/gitops-demo

If you intend to repeat the same instructions as presented within this lesson in your own environment, then you must FORK this repository into your own GitHub account. The reason for this, is that you need to be the owner of the repo to be able to upload and configure a new Deploy Key within the Settings area of the repo. The Settings area of a repo is only available when you are the owner of the repo.