containerization

Local PV (device) provisioner leaves a stale BDC in the following case:

• On PVC request, creates a BDC
• If the system doesn't have a matching BD, then PVC request keeps retrying, and so does the NDM operator that keeps retrying
• Now if the user deletes the PVC, then Local PV (device) provisioner doesn't get the trigger to process delete, as there was no PVC.

This causes the stale BDC

Is your feature request related to a problem?
"DevSpace should use the current docker behavior for dockerignore:
Dockerfile + .dockerignore
Dockerfile + Dockerfile.dockerignore
Dockerfile.frontend + Dockerfile.frontend.dockerignore
"

Which solution do you suggest?
Delegating the dockerignore file search to Docker if possible, otherwise copying the behavior as best as possible

As mentioned in discord I would recommend adding the following to your k3s deployment. I see multiple pages about the k3s deployment and each are missing the following which will make sure the nodes stay alive even if you over provision pods.

INSTALL_K3S_EXEC= ........ --kubelet-arg system-reserved=cpu=100m,memory=100Mi --kubelet-arg kube-reserved=cpu=200m,memory=400Mi

Jina includes a Monitor tab in the Console. The Monitor tab connects to a Jina Flow somewhere and displays all the Logs produced by that Flow in a graphical fashion.

Currently, the user can only stream logs from a Flow started by the Console. This happens in the Monitor tab of the Console.
![image](https://user-images.githubusercontent.com/23415764/123066358-46f5a100-d410-1