Change:
ephemeral-storage: "2Gi" limits: ephemeral-storage: "4Gi" <ins> volumeMounts: - name: ephemeral mountPath: "/tmp" </ins> - name: log-aggregator image: images.my-company.example/log-aggregator:v6 resources:

Discussion:
Looking at section: Local Ephemeral Storage The example YAML for ephemeral storage does not demonstrate the need for the volume or volume mount, it only shows the resource request form in the YAML as: From reading that documentation it's easy to assume that simply adding the resource request makes that amount of storage available to the containers root filesystem, which is not correct. The ephemeral-storage volume needs to be mounted as with: and But that is not captured in the documentation. At a minimum, the example YAML should include the volume and mount example to clarify this point. Otherwise, people (like me) will unwittingly assume they have 2Gi of space on the container root, which will likely work until a random unlucky day in the future leading to hard to debug issues.
Are you okay to close this now?
/language en
I think the best way to express that is to simply add the volume mounts to the example. This example is lacking volume mounts and so it's not clear unless you dig into the text to understand this detail. If you change that example to this it becomes a complete example in which the ephemeral-storage is actually mounted. As-is that example misleads the user to thinking that they have requested 2Gi of ephemerial-storage which is applied to their root filesystem.
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/triage accepted /language en
/help
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or .

/lifecycle rotten
/remove-lifecycle rotten
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle rotten
/assign
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close
Closing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/reopen
You can't reopen an issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/reopen /remove-lifecycle rotten
Reopened this issue. <detailsIn response to : /reopen /remove-lifecycle rotten Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details