Improvement for k8s.io/docs/reference/kubernetes-api/workload-resources/deployment-v1/

[briantkennedy]

DeploymentStatus has fields readyReplicas and availableReplicas. It's not clear what the difference is between availableReplicas and readyReplicas since the docs define these in terms of a pod being "ready", but don't define the criteria for "ready".

[shannonxtreme]

/triage accepted
/sig docs
/language en
/assign

Looks like it's not super clear what the difference is between "available" and "ready" in this context. A Pod has to be ready without its containers crashing for at least minReadySeconds to be considered "available".

availableReplicas is the number of available pods.
readyReplicas is the number of ready pods.

[kbhawkey]

Hi @briantkennedy .
This reference page is auto-generated from the code in kubernetes/kubernetes.
Unless there is a formatting issue, I would raise an issue upstream.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[shannonxtreme]

This was fixed in kubernetes/kubernetes/pull/103782

Thanks for the issue, @briantkennedy

/close

[k8s-ci-robot]

@shannonxtreme: Closing this issue.

In response to this:

This was fixed in kubernetes/kubernetes/pull/103782

Thanks for the issue, @briantkennedy

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.