Description
I downloaded multiple e2e-tests-report artifacts from main branch GitHub Actions runs of build-container.yml workflow for e.g. one of them is this one and observed that in all the reports the namespaces test showed the below report (indicating a false positive)
and the pods test showed the below report (indicating a flakiness)
I think this is the same issue that I was trying to highlight in this comment of mine on an on-going PR involving e2e-tests where I uploaded the below UI which I was seeing on performing a manual e2e-tests setup (as it is being done in the build-container.yml CI workflow) rather than using the minikube addon .
I think the current way we are setting up our e2e-tests environment in the build-container.yml CI workflow using kubernetes-headlamp-ci.yaml manifest is introducing too many plugins that are causing the UI to look very much different than an ideal scenario with just for e.g. a single pod-counter plugin.
The current implementation of these 2 tests is not matching up with the UI that is being rendered.
To Reproduce
Steps to reproduce the bug:
Perform a manual setup of the e2e-tests following build-container.yml workflow instead of using the minikube addon and visit the Headlamp UI and then try running these 2 tests on your local.
Environment (please provide info about your environment):
CI Workflow / Local e2e-tests Setup
Are you able to fix this issue?
[Yes (I can propose a PR after having a discussion with the maintainers about how to proceed for a fix)]