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. Hugo en-us Wed, 27 Mar 2024 10:40:21 -0400 http://localhost:8080/gitops_flux/5.prod/cicd/index.html Wed, 27 Mar 2024 10:40:21 -0400 http://localhost:8080/gitops_flux/5.prod/cicd/index.html Any commit to the main branch will trigger the CI/CD pipeline. In the repository, navigate to prod-cluster/deploy and edit deployment.yaml. Change the tag on the image: from 5.0.9 to 5.0.10 and commit the change. Navigate to Build then Pipelines. You should see the most recent pipeline run at the top with a status of blocked. Select the Blocked Status link. Select the run button to the right of the deploy_prod job. Select the deploy_prod job hyperlink to view the job status. http://localhost:8080/gitops_flux/5.prod/end/index.html Wed, 27 Mar 2024 10:40:21 -0400 http://localhost:8080/gitops_flux/5.prod/end/index.html That concludes the workshop. Questions/Feedback?