http://localhost:8080/gitops_flux/3.flux/index.html In this section we will configure the environment to enable Flux CD (https://fluxcd.io/) for continuous delivery in our staging environment. Flux has already been installed into the kubernetes (k8s) cluster, which is a one-time task for the administrator. First, we’ll run a CI/CD pipeline to upate yaml configuration files to make them specific to deploy into our staging k8s environment. The changes will be made into a new branch named staging. Hugo en-us Wed, 27 Mar 2024 10:40:21 -0400 http://localhost:8080/gitops_flux/3.flux/update_code/index.html Wed, 27 Mar 2024 10:40:21 -0400 http://localhost:8080/gitops_flux/3.flux/update_code/index.html There is a stage in the CI/CD configuration file (.gitlab-ci.yml) called staging that calls a script (update_code.sh) that edits all of the generic workshop yaml definitions and makes them specific for your deployment. For instance, it changes the namespace from USER-sandbox to have your username. It also does some base64 encoding using the CI/CD variables you created and adds them to k8s secret configuration files. Just like with the registry load, we are going to create a new branch to trigger this pipeline stage. Select Code then Branches. Select the New branch button, give it a name of staging and select Create branch. http://localhost:8080/gitops_flux/3.flux/create_secret/index.html Wed, 27 Mar 2024 10:40:21 -0400 http://localhost:8080/gitops_flux/3.flux/create_secret/index.html In the staging-cluster folder select the flux-secret.yaml file to review the file. Note that the namespace: is now our OpenShift namespace. In the data: section the password: field has been updated to a base64 encoded value of your ACCESS_TOKEN variable and the username is now a base64 encoded value of your username. After reviewing the changes, copy the contents of the entire file into your clipboard. http://localhost:8080/gitops_flux/3.flux/registry_secret/index.html Wed, 27 Mar 2024 10:40:21 -0400 http://localhost:8080/gitops_flux/3.flux/registry_secret/index.html OpenShift needs credentials to be able to pull the container images from the Gitlab container registry. The registry secret is a little trickier because of the unique docker configuration required. Back in Gitlab, copy the contents of the staging-cluster/registry-secret.yaml file to your clipboard. Make sure you copy the version from the staging branch and that you copy the entire file. Switch back to the OpenShift console. Select the + button in the upper right corner. Paste the contents of the secret and select the Create button on the bottom of the page. http://localhost:8080/gitops_flux/3.flux/gitlab/index.html Wed, 27 Mar 2024 10:40:21 -0400 http://localhost:8080/gitops_flux/3.flux/gitlab/index.html There are two special k8s objects that binds our git repository with Flux CD. The first one is of type GitRepository where we define our repository and credentials for the repository. The second is of type Kustomization which references the repository and defines the specific location for the application deployment files. Navigate back to Gitlab to the staging-cluster directory and make sure you are in the staging branch. Copy the gitrepository.yaml to your clipboard. Switch back to the OpenShift window select the + button in the upper right again to add content. Paste the content and select the Create button.