Скачать или смотреть Using `GitLab CI Variables in ArgoCD: A Step-by-Step Guide

Learn how to effectively use `GitLab CI variables` in your ArgoCD deployments by rethinking your deployment strategy and ensuring dynamic configuration.
---
This video is based on the question https://stackoverflow.com/q/76641761/ asked by the user 'Mohammad Reza Karimi' ( https://stackoverflow.com/u/12972198/ ) and on the answer https://stackoverflow.com/a/76642911/ provided by the user 'HiroCereal' ( https://stackoverflow.com/u/18099647/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How to use Gitlab CI variables in ArgoCD

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Use GitLab CI Variables in ArgoCD: A Step-by-Step Guide

In today's world of continuous deployment, tools like GitLab CI and ArgoCD are vital for managing your project deployments efficiently. However, transitioning from traditional CI/CD methods to a GitOps approach can be challenging. A common issue that many developers encounter is accessing CI variables, such as the ${CI_COMMIT_REF_SLUG}, when switching from GitLab pipelines to ArgoCD.
In this guide, we'll break down the steps to help you leverage GitLab CI variables in your ArgoCD setup effectively.

Understanding the Problem

You may have previously used a pipeline in GitLab with Helm to deploy your projects on Kubernetes. For instance, you set the deployment.containers[0].serviceNameTag to default to main, but occasionally, you needed to change it during deployment by using the --set command along with your variable ${CI_COMMIT_REF_SLUG}. Once you transition to ArgoCD for managing deployments, you might find yourself grappling with how to access these variables.

Embracing GitOps with ArgoCD

Rethink Your Deployment Strategy

Before we dive into the solution, it's essential to acknowledge that adopting GitOps does require a shift in mindset and process. ArgoCD is not merely a drop-in replacement for a traditional CD pipeline; instead, it operates under a different philosophy.

Key takeaway: You need to approach deployment in a way that aligns with the GitOps methodology. This might involve rethinking your deployment strategies to be more structured and predictable.

Solution: Using GitLab CI Variables in ArgoCD

Step 1: Prepare an Additional Step in Your Pipeline

One effective way to use GitLab CI variables in your ArgoCD configuration is to package your software in the pipeline. By doing this, you ensure a clear association between the deployed software and the specific Git commit it references.

Step 2: Modify the Helm Values File

You can easily modify your Helm values file to use the GitLab CI variable. To illustrate this, consider the following example using the yq tool, which is great for manipulating YAML files:

[[See Video to Reveal this Text or Code Snippet]]

In this command:

-i indicates that the operation should be done in-place.

The strenv(CI_COMMIT_REF_SLUG) will fetch the commit reference slug, allowing you to dynamically set the serviceNameTag in your Helm values.

Step 3: Deploy with ArgoCD

After modifying the Helm values using the above command, proceed with your ArgoCD deployment as usual. The serviceNameTag in your deployment will now reflect the current GitLab CI variable, enabling you to maintain consistency with your GitOps workflow.

Conclusion

Utilizing GitLab CI variables in ArgoCD requires a shift in how you think about deployments. By integrating steps into your pipeline that prepare your software to be deployed with dynamic configurations, you can seamlessly bridge the gap between your CI environment and the ArgoCD deployment model. Remember, the key to successfully implementing GitOps principles is to adapt your processes to favor clarity, consistency, and predictability.

Embrace these changes, and your transition from GitLab CI to ArgoCD will be smoother and more successful. Happy coding!