Explore updates to Production ArgoCD Manifests

  • In the previous section, we noted that a Merge Request has been raised on the Prod Argo manifest to update the prod image.

  • On Red Hat Developer Hub, in the parasol-store component’s Pull/Merge Requests page, you can view the a list of Gitlab Merge Request Statuses.

  • Click on the Revision link shown for parasol-store-prod. This will take you to the parasol-store-manifests repo showing the current commits to the parasol-store-manifests repository.

    parasol store deployment summary

  • From the left-hand navigation, access the Merge requests menu. Or click here to navigate to the Merge requests page.

  • You can see the Merge Request created for the parasol-store-manifests repo to update the prod image.

    parasol store prod pr

  • Click on the Changes tab, and you can see that the value-prod.yaml file is now updated to match the same image tag we noticed for the dev & staging deployments.

    parasol store prod pr changes

Merge updates to Production Argo Manifests

  • For the sake of the workshop, assume the persona of a release manager. Navigate back to the Overview tab of the Merge Request and proceed to Merge it.

    parasol store prod pr merge

  • Navigate to the Red Hat Developer Hub parasol-store component. From the CD tab, access the parasol-store-prod ArgoCD app by clicking on the arrow.

    parasol store go2argo

  • Click on the Refresh button.

    parasol store prod argo sync start

  • The Argo app will begin syncing.

    parasol store prod argo sync progress

  • In less than a minute, the new image will be deployed on Prod as well.

    parasol store prod argo sync done

    In ArgoCD, open the parasol-store deployment, and you can validate that the image deployed on Prod is the same image as in Dev and Staging that we saw earlier.

Conclusion

A developer can effortlessly set up an ephemeral development environment, build and test their code, and seamlessly advance it to production with the necessary guardrails in place.

All of this is accessible through a single-pane-of-glass experience on Red Hat Developer Hub, eliminating the need to switch between multiple tools and platforms to track both inner-loop and outer-loop progress and statuses.

The dynamic plugins that you enabled in previous modules provide incredible value to this experience by integrating real-time insights and providing contextual visibility, ensuring a smooth and efficient development lifecycle, there by reducing developer cognitive overload and streamlining the development lifecycle.