### What happened?

Kubelet-issued eviction always respects Pod.Spec.TerminationGracePeriodSeconds.

### What did you expect to happen?

Kubelet-issued eviction should NOT respect Pod.Spec.TerminationGracePeriodSeconds, which could be super long.

### How can we reproduce it (as minimally and precisely as possible)?

```yaml
apiVersion: v1
kind: Pod
metadata:
  name: foo
spec:
  containers:
  - name: busybox
    image: busybox:latest
    imagePullPolicy: IfNotPresent
    command: ['sh', '-c', 'echo Running ; sleep 3600']
    volumeMounts:
    - name: empty-dir-vol
      mountPath: /var/empty-dir
  volumes:
  - emptyDir:
      sizeLimit: "1Mi"
    name: empty-dir-vol
  terminationGracePeriodSeconds: 3600
```

- Create a Pod with the above Spec. 
- Then shell onto the Pod and execute `cd /var/empty-dir; dd if=/dev/zero of=largefile.txt bs=1M count=10` to create a file exceeds the volume limit.
- Observe the eviction being fired and Pod not killed.

### Anything else we need to know?

Although the eviction manager [set the grace period to be 0](https://github.com/kubernetes/kubernetes/blob/69b648a1d7074cbe004bf7adb3cdb17f01a4e9d8/pkg/kubelet/eviction/eviction_manager.go#L528C10-L528C18) in most cases, the value is always [overriden to Pod.Spec.TerminationGracePeriodSeconds](https://github.com/kubernetes/kubernetes/blob/69b648a1d7074cbe004bf7adb3cdb17f01a4e9d8/pkg/kubelet/pod_workers.go#L998).

### Kubernetes version

N/A

### Cloud provider

N/A

### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>

Kubelet eviction grace period overridden by Pod.Spec
This is a GitHub Issue
repo:kubernetes
owner:kubernetes
Title : Kubelet eviction grace period overridden by Pod.Spec
Issue date:

--- start body ---
### What happened?

Kubelet-issued eviction always respects Pod.Spec.TerminationGracePeriodSeconds.

### What did you expect to happen?

Kubelet-issued eviction should NOT respect Pod.Spec.TerminationGracePeriodSeconds, which could be super long.

### How can we reproduce it (as minimally and precisely as possible)?

```yaml
apiVersion: v1
kind: Pod
metadata:
  name: foo
spec:
  containers:
  - name: busybox
    image: busybox:latest
    imagePullPolicy: IfNotPresent
    command: ['sh', '-c', 'echo Running ; sleep 3600']
    volumeMounts:
    - name: empty-dir-vol
      mountPath: /var/empty-dir
  volumes:
  - emptyDir:
      sizeLimit: "1Mi"
    name: empty-dir-vol
  terminationGracePeriodSeconds: 3600
```

- Create a Pod with the above Spec. 
- Then shell onto the Pod and execute `cd /var/empty-dir; dd if=/dev/zero of=largefile.txt bs=1M count=10` to create a file exceeds the volume limit.
- Observe the eviction being fired and Pod not killed.

### Anything else we need to know?

Although the eviction manager [set the grace period to be 0](https://github.com/kubernetes/kubernetes/blob/69b648a1d7074cbe004bf7adb3cdb17f01a4e9d8/pkg/kubelet/eviction/eviction_manager.go#L528C10-L528C18) in most cases, the value is always [overriden to Pod.Spec.TerminationGracePeriodSeconds](https://github.com/kubernetes/kubernetes/blob/69b648a1d7074cbe004bf7adb3cdb17f01a4e9d8/pkg/kubelet/pod_workers.go#L998).

### Kubernetes version

N/A

### Cloud provider

N/A

### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>

--- end body ---

None