이제 핵심 장면입니다. 플러그인의 -w 옵션으로 전환 과정을 실시간으로 지켜봅니다.

$ kubectl argo rollouts get rollout notiflex-api -n notiflex -w
Name:            notiflex-api
Namespace:       notiflex
Status:          ◌ Progressing
Strategy:        BlueGreen
Images:          asia-northeast3-docker.pkg.dev/.../api:v0.1.1 (stable, active)
                 asia-northeast3-docker.pkg.dev/.../api:v0.2.0 (preview)
Replicas:
  Desired:       2
  Current:       4
  Updated:       2
  Ready:         4
  Available:     4
NAME                                              KIND        STATUS         AGE
⟳ notiflex-api                                    Rollout     ◌ Progressing  2m
├──# revision:2
│   └─⧉ notiflex-api-6b7c8d9e0f                   ReplicaSet  ✔ Healthy      15s  preview
│       ├─□ notiflex-api-6b7c8d9e0f-a1b2c          Pod         ✔ Running      15s  ready:1/1
│       └─□ notiflex-api-6b7c8d9e0f-d3e4f          Pod         ✔ Running      15s  ready:1/1
└──# revision:1
     └─⧉notiflex-api-1a2b3c4d5e                    ReplicaSet  ✔ Healthy      5m   stable
        ├─□ notiflex-api-1a2b3c4d5e-g6h7i          Pod         ✔ Running      5m   ready:1/1
        └─□ notiflex-api-1a2b3c4d5e-j8k9l          Pod         ✔ Running      5m   ready:1/1
# ... 30초 후 ...
Name:            notiflex-api
Namespace:       notiflex
Status:          ✔ Healthy
Strategy:        BlueGreen
Images:          asia-northeast3-docker.pkg.dev/.../api:v0.2.0 (stable, active)
Replicas:
  Desired:       2
  Current:       2
  Updated:       2
  Ready:         2
  Available:     2