# A PVC in sync wave 0 uses a StorageClass with volumeBindingMode WaitForFirstConsumer, and the Deployment that mounts it is in wave 1. What happens when Argo CD syncs?

Argo CD, Hard (Expert), Syncing & Deployment. https://k8wiz.com/uquiz/a-pvc-in-sync-wave-0-uses-a-storageclass-with-volumebindingmode-waitforfirstconsumer-and-the-deployment-that-mounts-it-is-in-wav

- A. Wave 1 starts after the 2 second wave delay, so the sync succeeds
- B. Argo CD binds the claim itself, so wave 1 starts once it is Bound
- C. Argo CD skips the health check for PVCs, so both waves apply at once
- D. The sync stalls, since the claim stays Pending until a Pod uses it

**Answer:** The sync stalls, since the claim stays Pending until a Pod uses it

**Explanation:** Argo CD waits for every resource in a wave to be healthy before it applies the next wave, and a PVC is Progressing while its phase is Pending. With WaitForFirstConsumer the claim only binds once a Pod using it is scheduled, but that Pod comes from the Deployment in wave 1. The 2 second ARGOCD_SYNC_WAVE_DELAY only spaces waves out and doesn't skip the health wait.
