Deployment “Replicas” row never shown

[Jay2006sawant]

Describe the bug

On the Deployment details page, the Replicas row in extra info is hidden even when Kubernetes has populated status.replicas, status.readyReplicas, etc.

showReplicas() checks item.spec?.status?.replicas, but Deployments do not have spec.status — replica counts live on status, not spec. This looks like a typo (spec.status vs status).

Expected: When a Deployment has replica counts in status, the Replicas row should appear (as renderReplicas() already reads from item.status).

Actual: The row stays hidden whenever spec.replicas is unset, even if status has replica data.

Evidence in code:

  function showReplicas(item: Workload) {
    return (
      item.kind === 'Deployment' &&
      (item.spec?.status?.replicas !== undefined || item.spec?.replicas !== undefined)
    );
  }

To Reproduce

1. Open Headlamp and connect to a cluster.
2. Find or create a Deployment where status.replicas / status.readyReplicas exist but spec.replicas is not present in the API response (or use a Deployment right after creation before spec is fully reflected).
3. Open the Deployment details page.
4. Observe that the Replicas row is missing under extra info, even though replica status exists in the object.

Environment (please provide info about your environment):

• Installation type: From source (npm start)
• Headlamp Version: main branch (app 0.42.0 in /app/package.json)
• Other: Reproducible in browser UI; logic bug in frontend/src/components/workload/Details.tsx

Are you able to fix this issue?

Yes (I will propose a PR)

Additional Context

• renderReplicas() (lines 153–158) already reads from item.status.* correctly — only the visibility guard is wrong.
• No existing GitHub issue found for spec.status.replicas / Deployment replicas row.
• Likely a long-standing typo, not a recent regression.

[Manar-Elhabbal7]

/assign

[Jay2006sawant]

Hey @Manar-Elhabbal7 , I am currently working on this.

[Manar-Elhabbal7]

Hey @Manar-Elhabbal7 , I am currently working on this.

yeah , sorry i didn't know

[kannon92]

Change makes sense to me.

Code is here.

/assign @Jay2006sawant

[sniok]

wait is this an actual issue? when does deployment api response lack spec.replicas?

even if you're creating a deployment without spec.replicas fields the api server will respond with default value of 1

[kannon92]

oc explain deployment.spec.status.replicas
GROUP:      apps
KIND:       Deployment
VERSION:    v1

error: field "replicas" does not exist

(item.spec?.status?.replicas !== undefined ||

That is for sure wrong at least.