Argo Rollouts misinterpreting init-style sidecar containers as normal initContainers

[rsavage-nozominetworks]

ISSUE DETAILS

---

Rollouts Version: 1.7.1 Rollouts Chart Version: 2.37.2 Kubernets Version: 1.30

When reviewing a rollout that includes an init-style sidecar container, both the UI and CLI (via the kubectl plugin) incorrectly interpret the status as a standard initContainer, resulting in the pod being displayed as not ready. Additionally, the pod's status, when viewed through either the UI or CLI, remains inaccurately stuck at "Init:0/X."

NAME                                                                    KIND         STATUS        AGE    INFO
⟳ demo-app-rollout                            Rollout      ✔ Healthy     19h
├──# revision:3
│  ├──⧉ demo-app-rollout-7988d84cd5           ReplicaSet   ✔ Healthy     37m   stable
│  │  ├──□ demo-app-rollout-7988d84cd5-6562s  Pod          ◌ Init:0/2    36m   ready:0/2  <---STUCK HERE
│  │  └──□ demo-app-rollout-7988d84cd5-sx6c4  Pod          ◌ Init:0/2    33m   ready:0/2  <---STUCK HERE
│  ├──α demo-app-rollout-7988d84cd5-3-1       AnalysisRun  ✔ Successful  36m   ✔ 3
│  ├──α demo-app-rollout-7988d84cd5-3-3       AnalysisRun  ✔ Successful  36m   ✔ 3
│  └──α demo-app-rollout-7988d84cd5-3-5       AnalysisRun  ✔ Successful  35m   ✔ 3,⚠ 1

Fortunately, the analysis runs complete, allowing the rollout to proceed. However, the status of the pod is concerning since it is actually active and ready. This issue is likely cosmetic but can still be misleading and needs to be fixed.

FUTHER DETAILS

---

• I noticed this other issue which seems to be related, and if it is, then I'd like to ask for some priority on this which is still in Draft.
• Kubernetes Sidecar container docs.