install/connect logging should be warnet CLI commands

[pinheadmz]

Because our new model is:

pip install warnet
cd some directory
warnet create ...
and so forth.

So the user shouldn't need to know where on their computer the install_logging.sh script is

[josibake]

Agree, and ideally they aren't even their own cli commands, but its an option set in a config file (e.g., the network.yaml) or something implicit like if you specifying logging on at least one node, then it auto installs logging.

[pinheadmz]

port forwarding too though! which is tricky because its a blocking process and ive found that port 3000 for grafana will occasionally drop out and either come back on its own or need to be reset

[josibake]

port forwarding too though!

paging @m3dwards , I think its time to kill port-forwarding with fire 😬 probably not essential for Tabconf, but I do think if we got some basic ingress/egress working at least for the dashboards, it would make the logging stuff much simpler from the user perspective (and ours).

[m3dwards]

Might be worth a discussion on pros / cons on ingress.

Downsides that come to mind is it's another small step to enable on minikube (just works on docker desktop) and that on cloud you get billed for public IP addresses and load balancers.

Benefit of ingress is it allows anyone to connect to the same service which is nice and might be a bit more reliable than port-forwarding.

[josibake]

started a discussion here re: port-forwarding vs ingress: #529