New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disambiguate Pod Phase from kubectl status... #46299
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
NAMESPACE NAME READY STATUS RESTARTS AGE | ||
alessandras-namespace alessandras-pod 0/1 CrashLoopBackOff 200 2d9h |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this indentation right?
{{< /note >}} | ||
|
||
|
||
{{< note >}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
{{< /note >}} | |
{{< note >}} | |
--- | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(this separator renders in the right color for a note callout, making it more obvious that a new callout is starting)
When a Pod is being deleted, it is shown as `Terminating` by some kubectl commands. | ||
This `Terminating` status is not one of the Pod phases. | ||
When a pod is not able to stay running, it may be shown as `CrashLoopBackoff` by some kubectl commands in its `Status`. | ||
Make sure not to confuse "Status", a display field for user intuition, with the pod "Phase", which is an explicit part of the Kubernetes data model. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might write:
Make sure not to confuse "Status", a display field for user intuition, with the pod "Phase", which is an explicit part of the Kubernetes data model. | |
Make sure not to confuse _Status_, a kubectl display field for user intuition, with the pod phase. | |
Pod phase is an explicit part of the Kubernetes data model and of the | |
[Pod API](/docs/reference/kubernetes-api/workload-resources/pod-v1/). |
@kubernetes/sig-node-pr-reviews how does this look? |
I don't understand why we have lost |
This PR disambiguates CrashLoopBackoff "Status" from the formal concept of the "Phase"...