http://localhost:8080/gitops_flux/index.html Description In this workshop you will use Flux CD (https://fluxcd.io/) with GitLab to deploy a container to an on-prem staging kubernetes (k8s) cluster. We’ll use GitLab CI/CD to download the container image from a web site and load it into a container registry hosted in GitLab. We’ll also use the CI/CD pipeline to deploy the application to a production k8s cluster hosted in Azure. Hugo en-us Wed, 27 Mar 2024 10:40:21 -0400 http://localhost:8080/gitops_flux/0.env/index.html Wed, 27 Mar 2024 10:40:21 -0400 http://localhost:8080/gitops_flux/0.env/index.html Following is a diagram of the workshop environment: http://localhost:8080/gitops_flux/1.setup/index.html Wed, 27 Mar 2024 10:40:21 -0400 http://localhost:8080/gitops_flux/1.setup/index.html The instructions for this lab are found here: https://neighborly-creator.azurewebsites.us/gitops_flux In this lab we’ll get connected to the lab environment and walk through the premise for the workshop. This is typically the hardest part of the workshop, if we can make it through this then it’s all smooth sailing! How it works The lab is in a private enclave which is not directly accessible over the internet. Workshop attendees are able to connect to specific services using a secure proxy with access controlled by Azure Active Directory. http://localhost:8080/gitops_flux/2.populate/index.html Wed, 27 Mar 2024 10:40:21 -0400 http://localhost:8080/gitops_flux/2.populate/index.html In this section we will user a Gitlab CI/CD pipeline to add content to the Gitlab container registry. Browse back to the repository. Select Code then Repository. Select the .gitlab-ci.yml file to view the contents. There are three stages in our pipeline. The first one is called registry. Notice in the load_registries: section there is a rule to run this stage when the commit branch is registry. When this stage executes it runs the images.sh script. Select the gitops-flux link to navigate back to the root of the repository. http://localhost:8080/gitops_flux/3.flux/index.html Wed, 27 Mar 2024 10:40:21 -0400 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. http://localhost:8080/gitops_flux/4.app/index.html Wed, 27 Mar 2024 10:40:21 -0400 http://localhost:8080/gitops_flux/4.app/index.html In the OpenShift browser, select Topology from the left menu. Click on the topology graphic in the middle to expand the topology. In the right, with the resources tab selected you should see Pods, Services and Routes. In the Routes section, select the URL to view the application. Note the version of the application. http://localhost:8080/gitops_flux/5.prod/index.html Wed, 27 Mar 2024 10:40:21 -0400 http://localhost:8080/gitops_flux/5.prod/index.html We are going to use a GitLab CI/CD pipeline to deploy our application in a push fashion to our production k8s cluster in Azure. Switch back to the main branch and review the files in prod-cluster/deploy folder. They look very similar to the yaml definition files in the staging directory. There are a few differences though. When your OpenShift accounts were provisioned, it automatically created you a namespace to work in. For Azure we must create a namespace as our first step using the namespace.yaml file.