<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>ArgoCD on Route179</title>
    <link>https://route179.dev/tags/argocd/</link>
    <description>Recent content in ArgoCD on Route179</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>2026 Sheng Chen</copyright>
    <lastBuildDate>Fri, 13 Sep 2024 20:36:31 +0000</lastBuildDate>
    <atom:link href="https://route179.dev/tags/argocd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>NKE Lab series – Ep5: Build a GitOps CD pipeline using GitHub, NKE and Argo CD</title>
      <link>https://route179.dev/2024/09/13/nke-lab-series-ep5-build-a-gitops-cd-pipeline-using-github-nke-and-argo-cd/</link>
      <pubDate>Fri, 13 Sep 2024 20:36:31 +0000</pubDate>
      <guid>https://route179.dev/2024/09/13/nke-lab-series-ep5-build-a-gitops-cd-pipeline-using-github-nke-and-argo-cd/</guid>
      <description>&lt;p&gt;This is the 5th episode of our &lt;a href=&#34;https://route179.dev/tags/nke/&#34;&gt;NKE lab series&lt;/a&gt;. In this episode, I will demonstrate how you can easily build a fully-automated GitOps continues delivery (CD) pipeline, by using Github, NKE and &lt;a href=&#34;https://argoproj.github.io/cd/&#34;&gt;Argo CD&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://about.gitlab.com/topics/gitops/&#34;&gt;GitOps&lt;/a&gt; is a operational framework that takes DevOps best practices (such as version control, Infra-as-Code, CI/CD etc), and applies them to modern and cloud native infrastructure such as Kubernetes-based clusters.&lt;/p&gt;
&lt;p&gt;There are two GitOps approaches: Push-based and Pull-based, and you can reach more about each model &lt;a href=&#34;https://www.harness.io/blog/gitops-the-push-and-pull-approach&#34;&gt;at here&lt;/a&gt;. This post will focus on the Pull-based approach as it provides many benefits such as better version control and governance, more automation and self-service capabilities, and easier for rollback, auditing/compliance suitable for large and stable production environment.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
