* Run e2e tests in k3s + helm rather than docker
* collect logs from k3s, use head and newer kube version, check for webhook up when starting rancher
* use latest rc chart
* debugging
* use lower kube version
* fixes to brittle tests, log fixes, enable oidc provider
* fix logs
* test tweaks
* use alpha repo, rc in stable is too old. also wait for capi service
* improvements
* debug
* rtryyr
* don't run settings e2e tests - they leave cluster with non-original values
* fix settings tests, fix CRD test (worked by luck before)
* fix fetch of initial settings
* more settings fixes, crd tweak
* update settings
- it uses useDefault as the reset, which was the issue
- leave tests as is (mosty) and just reset them all at the end
* asd
* adsad
* more settings fixes
* remove problem code
* use toms debug image for api failures
* sdfdsf
* Use 'head' chart
* Use audit log
* enable browser logs for beforeAll and afterAll
* debug for checking racnher pod containers, increase audit log level
* don't overwrite logs...
* output improvements, move position of audit log `set`
* use new (docs pending) flag to enable audit log
* extra logging now in rancher/rancher, use head image (should remove a lot of false positives around fleet)
* improve comment
* combine test artifacts
* tweaks, and another data point for 'resolved' tests
* attempt to get previous logs (audit log previous might not exist)
* remove k logs --previous, use logs deployment/name
* re-enable all tests
* tidyng up
* better logs, including crashed containers
* k3s updates... but run in docker
* change lookup from anything containing 1 to `1`
* changes following pr review
* remove un-needed chrome pin
- this commented out section was a c+p from the main e2e section
- the main e2e section comments this out
- both should use a single repo gh action, won't do that now though
Richard Cox
yonasberhe23
Yonas Berhe