Added the headers and maintained consistency

Signed-off-by: Aryan Shah <[email protected]>

Author: ARYANSHAH1567

content/challenges/11111111-1111-1111-1111-111111111111/configure-argo-cd-image-updater-challenge/content/argo-cd-image-updater-binary/_index.md

@@ -5,10 +5,12 @@ description: ""
 weight: 7
 ---
 
+### Testing Image Updates with argocd-image-updater
+
 The **argocd-image-updater** binary and specifically the **test** subcommand provides a variety of test options, including testing registry access, multi-arch images, semver constrains, update strategies, and credentials before configuring annotations on your Argo CD applications. It is available in the **argocd-image-updater** pod or you can install it locally. Here are the **argocd-image-updater** test command options:
 
 
-```
+``` bash
 Flags:
 
 --allow-tags string             only consider tags in registry that satisfy the match function

content/challenges/11111111-1111-1111-1111-111111111111/configure-argo-cd-image-updater-challenge/content/conclusions/_index.md

@@ -5,6 +5,8 @@ description: ""
 weight: 10
 ---
 
+### Conclusions
+
 The Argo CD Image Updater is a powerful tool that enhances the continuous delivery process in Kubernetes environments. Automating the process of updating container images not only streamlines deployments but also reduces the risk of human error associated with manual updates.
 
 Moreover, its flexibility allows developers to tailor the update policies to suit their specific workflows, ensuring that only the necessary updates are applied. This ultimately leads to improved application reliability and performance.

content/challenges/11111111-1111-1111-1111-111111111111/configure-argo-cd-image-updater-challenge/content/configuration-and-setup/_index.md

@@ -5,6 +5,9 @@ description: ""
 weight: 3
 ---
 
+### Setting Up Argo CD Image Updater
+
+
 In this example implementation, we are using the official [argocd-image-updater](https://github.com/argoproj/argo-helm/tree/main/charts/argocd-image-updater) Helm chart. It is deployed as an **argocd** application in the same cluster and namespace as Argo CD:
 
 ```yaml

content/challenges/11111111-1111-1111-1111-111111111111/configure-argo-cd-image-updater-challenge/content/enabling-service-account/_index.md

@@ -1,10 +1,12 @@
 ---
-id: "enabling-service-account-and-RBAC-creation"
-title: 'Enabling the Service Account and RBAC Creation'
+id: "service-account-and-RBAC"
+title: 'Service Account and RBAC'
 description: ""
 weight: 5
 ---
 
+### Enabling the Service Account and RBAC Creation
+
 ```yaml
 rbac:
   # -- Enable RBAC creation
@@ -26,7 +28,7 @@ serviceAccount:
 
 - **ServiceAccount** provides the necessary identity for ArgoCD Image Updater to authenticate and interact with the Kubernetes API to perform updates on deployment manifests or Helm charts (e.g., changing container image tags).
 
-- **rbac** ensures that ArgoCD Image Updater is granted only the permissions it needs, helping to secure your cluster by restricting its access and reducing the attack surface.
+- **RBAC** ensures that ArgoCD Image Updater is granted only the permissions it needs, helping to secure your cluster by restricting its access and reducing the attack surface.
 
 ---
 

content/challenges/11111111-1111-1111-1111-111111111111/configure-argo-cd-image-updater-challenge/content/log-level/_index.md

@@ -5,6 +5,8 @@ description: ""
 weight: 6
 ---
 
+### Configuring Log Levels in Argo CD Image Updater
+
 ```yaml
 # -- Argo CD Image Update log level
 logLevel: "debug"

content/challenges/11111111-1111-1111-1111-111111111111/configure-argo-cd-image-updater-challenge/content/overview/_index.md

@@ -1,10 +1,12 @@
 ---
-id: "Overview"
-title: 'Overview'
+id: "introduction"
+title: 'Introduction'
 description: ""
 weight: 1
 ---
 
+### Overview
+
 This challenge provides a walkthrough on automating Kubernetes deployments by integrating Argo CD Image Updater with Helm. It details the setup process, including configuring container registries like Amazon ECR and GitHub Container Registry, and emphasizes the importance of proper authentication and role-based access control (RBAC) to ensure secure and efficient operations. It also explores various update strategies—such as semantic versioning (semver), latest, digest, and name—demonstrating how to annotate Argo CD applications to enable these strategies effectively.
 
 ### Understanding Argo CD Image Updater

content/challenges/11111111-1111-1111-1111-111111111111/configure-argo-cd-image-updater-challenge/content/registires/_index.md

@@ -5,6 +5,8 @@ description: ""
 weight: 4
 ---
 
+### Configuring the container registries
+
 Let's configure the container registries that we are using. Argo CD Image Updater supports the majority of container registries (public and private), that implement Docker registry v2 API and has been tested against registries such as Docker Hub, Docker Registry v2 reference implementation (on-premise), Red Had Quay, Jfrog Artifactory, Github Container Registry, GitHub Packages Registry, GitLab Container Registry, and Google Container Registry.
 
 In the following examples, we will configure two of the most widely used container registries – Amazon Elastic Container Registry (ECR) and GitHub Container Registry (GHCR). In our case, we are working with private registries to ensure secure storage and access control for container images.
@@ -39,7 +41,7 @@ authScripts:
 The script is executed by the pod and is responsible for obtaining the ECR authorization token. We use a role attached to our EKS node group, which includes the AWS-managed policy **AmazonEC2ContainerRegistryReadOnly**. This policy permits the **GetAuthorizationToken** API call:
 
 
-```
+```bash
 {
     "Version": "2012-10-17",
     "Statement": [

content/challenges/11111111-1111-1111-1111-111111111111/configure-argo-cd-image-updater-challenge/content/update-methods/_index.md

@@ -5,6 +5,8 @@ description: ""
 weight: 8
 ---
 
+### Propagating New Image Versions in Argo CD
+
 Argo CD Image Updater supports two write-back methods for propagating new image versions to Argo CD.
 
 - **argocd**: 

content/challenges/11111111-1111-1111-1111-111111111111/configure-argo-cd-image-updater-challenge/content/update-strategies/_index.md

@@ -5,6 +5,8 @@ description: ""
 weight: 9
 ---
 
+### Update Strategies in Argo CD Image Updater
+
 An update strategy specifies how Argo CD Image Updater identifies new image versions for updates. It supports various strategies for tracking and updating configured images. Each image can have its update strategy, with the default being the semver strategy.
 
 The currently supported update strategies are:
@@ -23,7 +25,7 @@ In the examples below we show how to annotate our **argocd** applications to ena
 argocd-image-updater.argoproj.io/image-list: "<image_alias>=<some/image>"
 ```
 
-## semver update strategy:
+### semver update strategy:
 
 This is the default update strategy. Via the semver strategy, Argo CD Image Updater operates with images tagged in the semantic versioning format. Tags should include semver-compatible identifiers in the structure X.Y.Z, where X, Y, and Z are whole numbers. An optional prefix of “v” (for example, vX.Y.Z) can be used, and both formats are considered equivalent. In this first example, each annotation is specifically explained because we are using some of the annotations for the semver update strategy in all examples.
 
@@ -72,7 +74,7 @@ sampleapp:
       pullPolicy: "Always"
 ```
 
-## latest upadte strategy:
+### latest upadte strategy:
 
 Argo CD Image Updater can update the image with the most recent build date, even if the tag is arbitrary (like a Git commit SHA or random string). It focuses on the build date, not when the image was tagged or pushed to the registry. If multiple tags share the same build date, the updater sorts the tags in descending lexical order and selects the last one.
 
@@ -115,7 +117,7 @@ sampleapp:
 ```
 
 
-## digest update strategy:
+### digest update strategy:
 
 This update strategy monitors a specified tag in the registry for any changes and updates the image when a difference from the previous state is detected using the image SHA digest. The tag must be defined as a version constraint in the image list. It’s ideal for tracking mutable tags like the **latest** or environment-specific tags (e.g., **dev**, **stage**, **prod**) generated by a CI system.
 
@@ -150,7 +152,7 @@ deployment:
      pullPolicy: "Always"
 ```
 
-## name update strategy:
+### name update strategy:
 
 This updated strategy sorts image tags lexically in descending order and selects the last tag for updating. It’s useful for tracking images using calver versioning (e.g., YYYY-MM-DD) or similar tags. By default, all tags in the repository are considered, but you can configure it to limit which tags are eligible for updates.