Open manno opened 1 year ago
Elemental has CI to install RM- we can reuse that as 1st part of this pipeline work, i.e Fleet with Rancher Manager
From Rancher 2.9 onwards, it will be possible to configure alternative chart repositories, which should ease testing of any Fleet commit within Rancher.
Additional work, with WIP actions to release Fleet to a test charts repo for testing and using that to deploy Rancher through GCP-hosted Github runners, is available on branch test-fleet-in-latest-rancher.
We're waiting for Github Action private runners.
We need to request access to a non-containerised runner, see this. Latest progress available on this branch.
Non-containerised runners now work, but registering a downstream cluster times out in CI, although it works locally. We'd need to be able to know more about the state of Rancher on the runner to understand what prevents downstream cluster registration from working.
Could we run a pipeline against a fork (yes, physically possible), using a non-containerised runner (question sent to EIO in that regard, as per-repo authorisation is needed) with tmate (enabled temporarily until we find and fix the root cause of the issue)?
docs/testing_fleet_in_rancher.md
Rancher could be (nightly, rc, release).
How to install Rancher with our fleet build?
Running outside the cluster, without the rancher helm chart, could be interesting for vscode&integration tests E2e CI probably needs the modified image (or a branch in rancher/charts).
What are existing upgrade tests in Fleet:
How effective are our existing rancher integration tests?
fleet-upgrade-in-rancher.yaml
had a nice matrix)Problem
Do we observe downgrades to the released fleet chart?