Pods with Shutdown status confuse users of graceful node shutdown feature

[SergeyKanzhelev]

What happened:

When using Graceful Node Shutdown feature, status and reason of "shutdown" pod are confusing for users. See kubernetes/website#28235 where I attempt to address this confusion by documenting the behavior.

However, it would be great to improve messages. Perhaps the following renaming:

Status:         Failed. --------------------------------> Same
Reason:         Shutdown ----------------------------> Terminated 
Message:        Node is shutting, evicting pods ------> Pod was terminated in response to node shutdown.

Reason "Shutdown" is confusing because it may appear as a process of shutting down. Better message will also be useful.

What you expected to happen:

Reason and Message changed for pods terminated in response to Node shutdown.

How to reproduce it (as minimally and precisely as possible):

Shutdown the node and observer the pod status.

Anything else we need to know?:

KEP: kubernetes/enhancements#2000
/cc @bobbypage
/sig node
/help
/good-first-issue

Environment:

• Kubernetes version (use kubectl version): 1.19+ (with feature enabled)

[k8s-ci-robot]

@SergeyKanzhelev:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

What happened:

When using Graceful Node Shutdown feature, status and reason of "shutdown" pod are confusing for users. See kubernetes/website#28235 where I attempt to address this confusion by documenting the behavior.

However, it would be great to improve messages. Perhaps the following renaming:

Status:         Failed. --------------------------------> Same
Reason:         Shutdown ----------------------------> Terminated 
Message:        Node is shutting, evicting pods ------> Pod was terminated in response to node shutdown.

Reason "Shutdown" is confusing because it may appear as a process of shutting down. Better message will also be useful.

What you expected to happen:

Reason and Message changed for pods terminated in response to Node shutdown.

How to reproduce it (as minimally and precisely as possible):

Shutdown the node and observer the pod status.

Anything else we need to know?:

KEP: kubernetes/enhancements#2000
/cc @bobbypage
/sig node
/help
/good-first-issue

Environment:

• Kubernetes version (use kubectl version): 1.19+ (with feature enabled)

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.

[k8s-ci-robot]

@SergeyKanzhelev: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[ehashman]

/cc @rphillips @wgahnagl

[novahe]

/assign

[Hanvans]

/assign