You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Often times when issues are found and we need a log bundle, you can't deploy to the nodes in question. It would be good if Rancher ran a container or even an actual script loaded on the Node so that the user could manually collect a node's log bundle when K8s or Rancher are not operating. It seems to me that this tool depends on these two to be operational to deploy the log collecting daemonset.
The text was updated successfully, but these errors were encountered:
Often times when issues are found and we need a log bundle, you can't deploy to the nodes in question. It would be good if Rancher ran a container or even an actual script loaded on the Node so that the user could manually collect a node's log bundle when K8s or Rancher are not operating. It seems to me that this tool depends on these two to be operational to deploy the log collecting daemonset.
The text was updated successfully, but these errors were encountered: