We are upgraded to the last stable version 1.9.7.

Now, is not possible mount/inject only one file without affected other files in a directory?

If I use subPath with fileName "caused "not a directory"" error is raised.

There are no solutions for this problem jet?. I'm reading a lot of related issues and try different examples with no success.

Hi @vrubiella, are you trying to nest a subPath mount underneath another volume mount? If so, then you may be hitting #61545

is #63045 related?

@pawelprazak yes, but actually, that fix caused another regression, which has been fixed by #64351

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

We do not plan to address the two remaining issues in the near term:
#61446: volume reconstruction does not work with host path volumes mounted via subPath. We eventually hope to address this by refactoring volume reconstruction to use kubelet checkpointing.
#61545: subpath mounts nested within atomic writer volumes (configmap, secret, downwardAPI, projected) do not work. Fixing this would require an api change to tell kubernetes whether to create a file or directory. It's unclear whether this use case is common enough to warrant such a change, or if the workarounds are sufficient.

/close

@msau42: Closing this issue.