Separate feature for local host machine file save.

[Tatsinnit]

As a day 1 behaviour one of a very enabling feature is to upload the node logs to the azure storage We could scope how to store file locally if user choose to go that way.

Below is some thoughts ☕️❤️ for trying a POC (Proof of concept) to see if we can get files form pods to local host machine.

Currently its just idea and this needs proper approach for understanding file-system usage of pod etc. Because currently there is no direct to mount hostPath from host machine to pod, so what we need is to use the client-go copy feature. Details below.

Use Case

As a user if I opt-in for the logs to be saved locally to a specific location in host file-system.

Now something which this use-case needs user to understand is that how old is node, how big is their node and if there is enough space in their node.

We have improved a lot in recent month in periscope as tool and we handle file writing in memory and then directly store it to the storage which give us no-dependency on user file system, although with this feature enablement all user need to aware that we will temporary save the log in their node before we copy them to the host machine.

Advantage

There is no consuming tool which has this behaviour but if used correctly this could avoid the whole storage path altogether.

Thanks heaps.