FluxCD for continuous delivery in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is FluxCD in the context of Kubernetes?

FluxCD is a tool that automates the deployment of container images and configuration changes to Kubernetes clusters, enabling continuous delivery by syncing Git repositories with the cluster state.

beginner

How does FluxCD use Git in continuous delivery?

FluxCD treats Git as the single source of truth. It continuously monitors Git repositories for changes and applies those changes automatically to the Kubernetes cluster, ensuring the cluster matches the desired state defined in Git.

intermediate

What is a GitRepository resource in FluxCD?

A GitRepository resource in FluxCD defines the location and credentials of a Git repository that FluxCD will watch for changes to deploy to the Kubernetes cluster.

intermediate

Explain the role of the Kustomization resource in FluxCD.

The Kustomization resource tells FluxCD which manifests to apply from the Git repository, how often to sync, and how to handle dependencies, enabling customization of Kubernetes resources during deployment.

beginner

What happens if the Kubernetes cluster drifts from the desired state in Git when using FluxCD?

FluxCD detects the drift and automatically reconciles the cluster back to the desired state defined in Git, ensuring consistency and reliability in deployments.

What is the main purpose of FluxCD?

A Monitor Kubernetes cluster health

B Build container images from source code

C Automate continuous delivery by syncing Git with Kubernetes

D Manage Kubernetes user access

FluxCD automates continuous delivery by syncing Git repositories with Kubernetes clusters.

Which resource in FluxCD defines the Git repository to watch?

A Kustomization

B GitRepository

C HelmRelease

D Pod

GitRepository resource specifies the Git repo FluxCD monitors for changes.

How does FluxCD handle changes made directly in the Kubernetes cluster that differ from Git?

A Reconciles cluster back to Git state

B Overrides Git with cluster changes

C Ignores them

D Sends an alert but does nothing

FluxCD reconciles the cluster to match the Git repository state automatically.

What does the Kustomization resource in FluxCD do?

A Specifies which manifests to apply and sync frequency

B Defines how to build container images

C Manages user permissions

D Monitors cluster resource usage

Kustomization tells FluxCD which manifests to apply and how often to sync.

FluxCD is an example of which deployment approach?

A Manual deployment

B Blue-green deployment

C Canary deployment

D GitOps

FluxCD follows the GitOps approach, using Git as the source of truth for deployments.

Describe how FluxCD enables continuous delivery in Kubernetes using Git repositories.

Think about how FluxCD watches Git and applies changes to the cluster.

Explain the role of the Kustomization resource and how it helps manage deployments in FluxCD.

Consider how FluxCD knows what and when to deploy from Git.