GitOps with ArgoCD in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to install ArgoCD in the Kubernetes cluster.

Kubernetes

kubectl create namespace [1]

Drag options to blanks, or click blank then click option'

Akube-system

Bdefault

Cargocd

Dargo

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'default' namespace instead of 'argocd'.

Using 'kube-system' which is reserved for system components.

The namespace argocd is the default namespace where ArgoCD is installed.

2fill in blank

medium

Complete the kubectl command to apply the ArgoCD installation manifest from the official URL.

Kubernetes

kubectl apply -n argocd -f [1]

Drag options to blanks, or click blank then click option'

Ahttps://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/delete.yaml

Bhttps://example.com/install.yaml

Chttps://raw.githubusercontent.com/kubernetes/website/main/content/en/examples.yaml

Dhttps://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml

Attempts:

3 left

💡 Hint

Common Mistakes

Using a URL that points to unrelated manifests.

Using a URL for deletion instead of installation.

The official ArgoCD installation manifest is hosted at the stable branch URL under the argoproj GitHub repository.

3fill in blank

hard

Fix the error in the command to get the ArgoCD server service details.

Kubernetes

kubectl get svc -n argocd [1]

Drag options to blanks, or click blank then click option'

Aargocd-server

Bargocd-service

Cargo-server

Dserver-argocd

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect service names that do not exist.

Swapping the order of words in the service name.

The ArgoCD server service is named argocd-server in the argocd namespace.

4fill in blank

hard

Fill both blanks to create an ArgoCD application manifest snippet that syncs from a Git repo.

Kubernetes

"apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: guestbook
spec:
  source:
    repoURL: [1]
    path: guestbook
  destination:
    server: [2]
    namespace: default"

Drag options to blanks, or click blank then click option'

Ahttps://github.com/argoproj/argocd-example-apps.git

Bhttps://github.com/example/repo.git

Chttps://kubernetes.default.svc

Dhttps://example.com/api

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect or non-existent Git repo URLs.

Using external URLs instead of the Kubernetes API server URL.

The repoURL should point to the official ArgoCD example apps repository. The destination.server is the internal Kubernetes API server URL https://kubernetes.default.svc.

5fill in blank

hard

Fill both blanks to complete the command to log into ArgoCD CLI with the admin password from the secret.

Kubernetes

argocd login localhost:[1] --username admin --password $(kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | [2])

Drag options to blanks, or click blank then click option'

A8080

Bbase64 -d

Cbase64 --decode

D80

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong port numbers like 80.

Using incorrect base64 decoding flags.

Not decoding the password from base64.

The ArgoCD server usually listens on port 8080 locally. The password is stored base64 encoded in the secret under .data.password and must be decoded with base64 --decode.

Practice

1. What is the main purpose of using ArgoCD in a Kubernetes environment with GitOps?

easy

A. To replace Kubernetes with a new container orchestration system

B. To manually deploy applications without using Git

C. To store container images in a private registry

D. To automatically sync Kubernetes cluster state with Git repository configurations

Solution

1. Step 1: Understand GitOps concept

   GitOps uses Git as the single source of truth for application configurations.

2. Step 2: Role of ArgoCD in GitOps

   ArgoCD automatically syncs Kubernetes cluster state to match the Git repo, ensuring deployments are consistent and automated.

3. Final Answer:

   To automatically sync Kubernetes cluster state with Git repository configurations -> Option D

4. Quick Check:

   GitOps = Auto-sync cluster with Git [OK]

Hint: Remember: ArgoCD syncs cluster state from Git automatically [OK]

Common Mistakes:

• Thinking ArgoCD replaces Kubernetes
• Believing ArgoCD deploys apps manually
• Confusing ArgoCD with container registries

2. Which of the following is the correct ArgoCD CLI command to create an application named myapp syncing from Git repo https://github.com/example/repo.git with path k8s and target cluster https://kubernetes.default.svc?

easy

A. argocd app create myapp --repo https://github.com/example/repo.git --path k8s --dest-server https://kubernetes.default.svc --dest-namespace default

B. argocd create app myapp --repository https://github.com/example/repo.git --directory k8s --cluster https://kubernetes.default.svc

C. kubectl create app myapp --repo https://github.com/example/repo.git --path k8s

D. argocd app new myapp --repo-url https://github.com/example/repo.git --folder k8s --server https://kubernetes.default.svc

Solution

1. Step 1: Identify correct ArgoCD CLI syntax

   The correct command uses argocd app create with flags --repo, --path, --dest-server, and --dest-namespace.

2. Step 2: Compare options

   argocd app create myapp --repo https://github.com/example/repo.git --path k8s --dest-server https://kubernetes.default.svc --dest-namespace default matches the official syntax exactly. Others use incorrect commands or flags.

3. Final Answer:

   argocd app create myapp --repo https://github.com/example/repo.git --path k8s --dest-server https://kubernetes.default.svc --dest-namespace default -> Option A

4. Quick Check:

   Correct CLI syntax = argocd app create myapp --repo https://github.com/example/repo.git --path k8s --dest-server https://kubernetes.default.svc --dest-namespace default [OK]

Hint: Remember: 'argocd app create' plus repo, path, dest-server flags [OK]

Common Mistakes:

• Using kubectl instead of argocd CLI
• Wrong flag names like --repository or --folder
• Incorrect command order or missing --dest-namespace

3. Given the following ArgoCD Application YAML snippet, what will happen when ArgoCD syncs this app?

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: sample-app
spec:
  source:
    repoURL: https://github.com/example/app-configs.git
    path: production
  destination:
    server: https://kubernetes.default.svc
    namespace: default
  syncPolicy:
    automated: {}

medium

A. ArgoCD will reject the app because syncPolicy is empty

B. ArgoCD will only show the app status but not deploy it automatically

C. ArgoCD will automatically deploy and keep the app in sync with the Git repo

D. ArgoCD will deploy the app once but not update it on Git changes

Solution

1. Step 1: Understand syncPolicy automated

   The syncPolicy: automated: {} means ArgoCD will auto-sync changes from Git to cluster.

2. Step 2: Effect on deployment

   ArgoCD will deploy the app initially and keep it updated automatically when Git changes.

3. Final Answer:

   ArgoCD will automatically deploy and keep the app in sync with the Git repo -> Option C

4. Quick Check:

   syncPolicy automated = auto deploy and sync [OK]

Hint: syncPolicy automated means auto deploy and keep in sync [OK]

Common Mistakes:

• Thinking empty braces mean no automation
• Assuming manual sync is required
• Confusing syncPolicy with app rejection

4. You created an ArgoCD app but it shows OutOfSync status even after you committed changes to Git. Which of the following is the most likely cause?

medium

A. The app's syncPolicy is not set to automated, so manual sync is needed

B. The Git repository URL is incorrect and unreachable

C. The Kubernetes cluster is down and cannot apply changes

D. The app name in ArgoCD does not match the Git repo name

Solution

1. Step 1: Understand OutOfSync status

   OutOfSync means cluster state differs from Git repo state.

2. Step 2: Check syncPolicy effect

   If syncPolicy is not automated, ArgoCD won't auto-apply changes; manual sync is required.

3. Final Answer:

   The app's syncPolicy is not set to automated, so manual sync is needed -> Option A

4. Quick Check:

   OutOfSync + no automated sync = manual sync needed [OK]

Hint: OutOfSync often means no automated sync set [OK]

Common Mistakes:

• Assuming cluster is down without checking
• Blaming Git URL without error evidence
• Thinking app name mismatch causes OutOfSync

5. You want to ensure that ArgoCD only deploys changes to your Kubernetes cluster after manual approval, but still track changes in Git automatically. Which configuration should you use in your ArgoCD Application YAML?

hard

A. Set syncPolicy: automated: {} to enable auto deploy

B. Omit syncPolicy and use manual sync to approve changes

C. Set syncPolicy: automated: null to disable auto deploy

D. Set syncPolicy: automated: { prune: true, selfHeal: true } for auto deploy with cleanup

Solution

1. Step 1: Understand manual approval need

   To require manual approval before deployment, auto sync must be disabled.

2. Step 2: Configure syncPolicy accordingly

   Omitting syncPolicy disables auto sync, so ArgoCD tracks Git but waits for manual sync.

3. Final Answer:

   Omit syncPolicy and use manual sync to approve changes -> Option B

4. Quick Check:

   No syncPolicy = manual approval required [OK]

Hint: No syncPolicy means manual sync only [OK]

Common Mistakes:

• Using automated sync disables manual approval
• Setting automated with prune/selfHeal still auto deploys
• Setting automated: null is invalid syntax