-
Notifications
You must be signed in to change notification settings - Fork 329
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
HostTailes / fileTailers: ability to mount additional hostPaths more easily #1462
Comments
Hey @PlayMTL, thanks for opening this issue! Could you please share some more details?
You mentioned that it is a symlinked directory. Would it be possible to mount the original folder instead? |
Hey @OverOrion, thanks for your reply.
You mentioned that it is a symlinked directory. Would it be possible to mount the original folder instead?
We have also checked it and it seems that on rke2 that path is no longer a symlink, so mounting it should work on rke2. |
is RKE1 something that will stick, or do you expect to upgrade from it one day? anyone else having the same issue? just would like to understand how much benefit we would have if we fix this on the long run... |
I have the same issue with some production clusters. There is no upgrade path given by the vendor and no plans for EOL it from now on. |
@PlayMTL you can also reach out over our project discord in case you want to have a chat: https://discord.gg/sXFdDKEKK8 |
Is your feature request related to a problem? Please describe.
The Rancher Kubernetes Engine (RKE) creates a directory "/var/lib/rancher/rke/log" from which log files under "/var/lib/docker/containers" are then pointed to via symlink. The Problem is, that the path /var/lib/docker/containers is not mounted, because the defined path in the fileTailers of the HostTailers is "/var/lib/rancher/rke/log". So the target file cannot be found in the fluentbit container because the host path has not been mounted.
Describe the solution you'd like
It would be cool if you could simply define additional "mount paths" in the fileTailers without configuring additional volume mounts.
Describe alternatives you've considered
My current workaround looks like this:
Additional context
Is a little bit related to: #984
The text was updated successfully, but these errors were encountered: