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
Currently, the logs collector in e2e tests gathers only the cluster description from the clusterctl output, along with logs from the CAPI, CAPA, CAPV, CAPZ providers, and the KCM controller. But, this data is insufficient for effective debugging.
To improve issue diagnosis, it should also collect at least all cluster-related objects, including their specs and statuses, as well as logs from K0smotron and CAPO, capture existing templates, Helm charts, Helm releases, and other relevant resources.
The text was updated successfully, but these errors were encountered:
Currently, the logs collector in e2e tests gathers only the cluster description from the
clusterctl
output, along with logs from the CAPI, CAPA, CAPV, CAPZ providers, and the KCM controller. But, this data is insufficient for effective debugging.To improve issue diagnosis, it should also collect at least all cluster-related objects, including their specs and statuses, as well as logs from K0smotron and CAPO, capture existing templates, Helm charts, Helm releases, and other relevant resources.
The text was updated successfully, but these errors were encountered: