Merge pull request #55 from taufiqpsumarna/staging

Staging
taufiqpsumarna · Jan 9, 2025 · d3b919b · d3b919b
2 parents f14afbc + ce0dc20
commit d3b919b
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 4 deletions.
diff --git a/docs/assets/images/win11wsl.png b/docs/assets/images/win11wsl.png
diff --git a/docs/blog/posts/2024/12/journey-to-argocd.md → docs/blog/2025/01/journey-to-argocd.md b/docs/blog/posts/2024/12/journey-to-argocd.md → docs/blog/2025/01/journey-to-argocd.md
@@ -1,17 +1,16 @@
 ---
-draft: true #Todo: Change False to post Blog
+draft: false #Todo: Change False to post Blog
 authors: 
   - taufiqpsumarna
 title: "Effortless CI/CD: Integrating ArgoCD into Kubernetes Workflows" #Todo: Add Blog Title
-date: 2024-12-27 #Todo: Change Date 
+date: 2025-01-10 #Todo: Change Date 
 description: "Effortless CI/CD: Integrating ArgoCD into Kubernetes Workflows" #Todo: Add Short Description / Subtitle
 categories: [Blog] #Todo: Categories Blog, Medium, Other
 tags: [devops,docker,kubernetes,argocd,helm,gitlab,cicd,gitops] #Todo: Add Blog Tags
 ---
 
 ![How to Reduce Docker Image Size and Ensure Security in Your Docker Images](/assets/images/IntegratingArgoCDintoKubernetesWorkflows.png)
 
-
 In today’s fast-paced DevOps landscape, continuous integration and continuous depaloyment (CI/CD) pipelines have become a cornerstone of efficient software delivery. Kubernetes, with its scalability and flexibility, has been a favorite among engineers for orchestrating containerized applications. However, traditional deployment methods using raw Kubernetes manifests can often become cumbersome and error-prone. This is where **GitOps** and tools like **ArgoCD** come to the rescue. Let’s dive into how to integrate ArgoCD into Kubernetes workflows and explore why GitOps is a game-changer for modern CI/CD pipelines.
 
 ---

diff --git a/docs/blog/posts/2024/12/win11-wsl.md b/docs/blog/posts/2024/12/win11-wsl.md
@@ -51,7 +51,7 @@ Developers and tech enthusiasts often find themselves navigating between the rob
 By default, WSL can use as much memory as it needs, potentially consuming significant resources, especially during intensive tasks like compiling code or running multiple processes, to ensure balanced resource allocation between your Windows host system and the Linux environment running in WSL we need to limit WSL memory in `.wslconfig`
 
 1. Create or edit the `.wslconfig` file in `C:\Users\<username>\.wslconfig`.
-2. Create new files in notepad and add the following configuration to limit resources:
+2. add the following configuration to limit resources:
 
    ```ini
    [wsl]