Table of Contents

1. Challenge

   Create a GitHub Repository Under Your Own Account

   To create a repository on GitHub you must log in to your own account, and then you can create a repository with the YAML files you require. Or you can find the linuxacademy/content-gitops repository and fork it. Once you create your own version of that repository, examine the YAML files in the namespaces and workloads folders.

2. Challenge

   Deploy Flux Into Your Cluster

   To check whether fluxctl is installed, enter:

   $ fluxctl version
   

   If fluxctl did not install automatically, you may enter the following command to install it:

   $ sudo wget https://github.com/fluxcd/flux/releases/download/1.25.4/fluxctl_linux_amd64 -O /usr/bin/fluxctl && sudo chmod +x /usr/bin/fluxctl
   

   Create a namespace for Flux:

   $ kubectl create ns flux
   

   Set the GHUSER environment variable:

   $ export GHUSER=[Your GitHub Handle]
   

   Deploy Flux using the fluxctl command:

   $ fluxctl install 
   --git-user=${GHUSER} 
   --git-email=${GHUSER}@users.noreply.github.com 
   [email protected]:${GHUSER}/content-gitops 
   --git-path=namespaces,workloads 
   --namespace=flux | kubectl apply -f -
   

3. Challenge

   Verify The Deployment and Obtain the RSA Key

   Verify the Flux deployment:

   $ kubectl -n flux rollout status deployment/flux
   

   Obtain the Flux RSA key created by fluxctl:

   $ fluxctl identity --k8s-fwd-ns flux
   

   Copy off the RSA key to implement in GitHub.

4. Challenge

   Implement the RSA Key in GitHub

   Use the GitHub User Interface to Add the RSA Key obtained as a Deploy Key in GitHub.

5. Challenge

   Use the fluxctl sync Command to Synchronize the Cluster with the Repository

   Use fluxctl to sync the cluster with the repository:

   $ fluxctl sync --k8s-fwd-ns flux
   

   Then check the existence of the lasample namespace:

   $ kubectl get namespaces
   

   Finally check that the Nginx deployment is running:

   $ kubectl get pods --all-namespaces