Add K8s logging in the CI when QHub deploy fails

[aktech]

At the moment when the K8s deploy fails, there is not much information for the user in the CI logs for the user to figure out the root cause of the problem.

A nice approach would be to have a step run on failure, which logs everything from the minikube kubernetes cluster. I have done something similar in https://github.com/dask/dask-gateway

[Adam-D-Lewis]

@tylerpotts This could possibly affect our debugging of the monitoring PR where the kubernetes tests are failing.

[costrouc]

@aktech I was thinking that we could tie in https://github.com/Quansight/qhub/issues/771 to this issue. The idea would be to run qhub support on failure or something similar to create an artifact on failure that could be used for inspection.

[aktech]

@costrouc sounds great, would be great if we can print that in the CI step itself instead of an artifact.

[costrouc]

Sounds great to me. We'll make sure that the support command does that as well.

[github-actions[bot]]

This issue has been automatically marked as stale because there was no recent activity in 60 days. Remove the stale label or add a comment, otherwise, this issue will automatically be closed in 7 days if no further activity occurs.

[github-actions[bot]]

This issue was closed because it has been stalled for 7 days with no activity.

[iameskild]

If CI fails, run the nebari support tool and save the output.

[iameskild]

I think for now we can consider this closed. The nebari support grabs a bunch of k8s logs and saves them to the user's local machine in case they want to review them or share them with us over an issue.