FluxCD for continuous delivery in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

FluxCD GitRepository Resource Status Check

You run the command kubectl get gitrepositories.source.toolkit.fluxcd.io after applying a GitRepository manifest. What output indicates the repository is successfully cloned and ready?

Kubernetes

kubectl get gitrepositories.source.toolkit.fluxcd.io

A

NAME          READY   STATUS              REVISION          SUSPENDED
my-repo       True    Fetched revision    main@abcdef1234   False

B

NAME          READY   STATUS              REVISION          SUSPENDED
my-repo       False   Cloning failed      main@abcdef1234   False

C

NAME          READY   STATUS              REVISION          SUSPENDED
my-repo       True    Cloning in progress main@abcdef1234   False

D

NAME          READY   STATUS              REVISION          SUSPENDED
my-repo       False   Repository not found main@abcdef1234  False

💡 Hint

Look for READY status being True and a positive STATUS message.

FluxCD marks the GitRepository resource as READY True when it successfully clones and fetches the revision. Other statuses indicate errors or ongoing processes.

🔀 Workflow

intermediate

FluxCD Automated Deployment Workflow

Which step correctly describes the order of actions FluxCD performs to deploy an application from a Git repository?

A 1,2,3,4

B 2,1,3,4

C 3,1,2,4

D 1,3,2,4

💡 Hint

Think about fetching code before applying it.

FluxCD first fetches the latest code, then applies manifests, monitors state, and finally updates status.

❓ Troubleshoot

advanced

Diagnosing FluxCD Kustomization Sync Failure

You see the Kustomization resource stuck with Ready: False and status message Reconciliation failed: unable to apply manifests. Which command helps you find detailed error logs for this Kustomization?

A kubectl logs -n flux-system deployment/flux-controller

B kubectl describe kustomization -n flux-system my-kustomization

C kubectl logs -n flux-system kustomization/my-kustomization

D kubectl get events -n flux-system --field-selector involvedObject.name=my-kustomization

💡 Hint

Look for detailed status and error messages in resource description.

The kubectl describe command on the Kustomization resource shows detailed status and error messages explaining why reconciliation failed.

🧠 Conceptual

advanced

Understanding FluxCD Reconciliation Interval

What is the effect of setting a very short reconciliation interval (e.g., 5 seconds) on a FluxCD Kustomization resource?

A FluxCD will ignore changes and only reconcile once at startup.

B FluxCD will batch changes and apply them once every hour regardless of interval.

C FluxCD will frequently check and apply changes, increasing cluster load and API server requests.

D FluxCD disables reconciliation and requires manual sync commands.

💡 Hint

Think about how often FluxCD polls the Git repository and applies manifests.

A short reconciliation interval causes FluxCD to check for changes very often, which can increase load on the cluster and Git server.

✅ Best Practice

expert

Secure Git Access in FluxCD

Which method is the most secure and recommended way to provide FluxCD access to a private Git repository?

A Allow anonymous read access to the Git repository to avoid credentials.

B Store Git username and password in plain text in the Kustomization manifest.

C Embed personal access tokens directly in the Git URL in the manifest.

D Use SSH deploy keys stored as Kubernetes secrets referenced by FluxCD GitRepository resource.

💡 Hint

Consider security best practices for credentials in Kubernetes.

Using SSH deploy keys stored securely as Kubernetes secrets and referenced by FluxCD is the recommended secure method.