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
Since the CLI revamp, and UI installation addition, the verbose logs now only display, except for a k3d installation, the logs for cluster 0, which is the cluster used to get console as an UI installer when using the UI, or the local cluster used to contact the API when using the CLI directly. A lot happens in cluster 1 pods logs, like with the API pod. Right now the user need to get the KUBECONFIG of their cloud cluster, and manually check the logs in the pods to get more information about the process or find any possible errors. Until kubefirst/kubefirst#2032 is implemented, we need to be clear about logs in the docs.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
What type of suggestions?
Missing Information
What page is concerned?
No response
What version of the docs?
2.3+
What is the issue?
Since the CLI revamp, and UI installation addition, the verbose logs now only display, except for a k3d installation, the logs for cluster 0, which is the cluster used to get console as an UI installer when using the UI, or the local cluster used to contact the API when using the CLI directly. A lot happens in cluster 1 pods logs, like with the API pod. Right now the user need to get the KUBECONFIG of their cloud cluster, and manually check the logs in the pods to get more information about the process or find any possible errors. Until kubefirst/kubefirst#2032 is implemented, we need to be clear about logs in the docs.
Code of Conduct
The text was updated successfully, but these errors were encountered: