Certified Argo Project Associate (CAPA) free question 8 / 10 · Domain 3: Argo Rollouts
A canary Rollout defines the steps setWeight: 20, pause: {}, setWeight: 25. The controller reaches the pause step. What happens next?
- The rollout waits for a default of ten minutes and then moves on to the setWeight: 25 step of the strategy
- The rollout is marked as failed, as a pause step needs a duration field to be valid
- The rollout waits indefinitely until the pause condition is removed, for example by a promote command
- The rollout skips the pause step, as the Rollout does not use traffic management
Show the answer and explanation
Answer: C
Why this is correct
The Canary page explains that when the controller reaches a pause step, it adds a PauseCondition to the Rollout status. If the pause struct sets a duration, the rollout does not progress until that time has passed. Otherwise the rollout waits indefinitely until the pause condition is removed. To unpause, the kubectl argo rollouts promote command moves the rollout on to the next step.
Why the other options are wrong
"The rollout waits for a default of ten minutes and then moves on to the setWeight: 25 step of the strategy" … A pause step has no default length. Without a duration field the rollout waits indefinitely. When a duration is given without a unit suffix, it is read in seconds.
"The rollout is marked as failed, as a pause step needs a duration field to be valid" … The duration field is optional. A pause step with an empty body is valid and is the documented way to pause indefinitely.
"The rollout skips the pause step, as the Rollout does not use traffic management" … Pause steps are evaluated with or without traffic management. The controller adds a pause condition to the status of the Rollout when it reaches the step.
Key points
pause: {} waits until someone promotes. pause with a duration resumes by itself after that time.