Rename Fleet GitRepo names in E2E tests to be more specific, including the provider and Kubernetes distribution.
Add a random suffix to generated GitRepo names in the test framework to ensure uniqueness and prevent conflicts.
Signed-off-by: Danil-Grigorev <danil.grigorev@suse.com>
* Refactor e2e to use env declaratively
Signed-off-by: Danil-Grigorev <danil.grigorev@suse.com>
* Default policy to IfNotPresent in e2e
Signed-off-by: Danil-Grigorev <danil.grigorev@suse.com>
* Simplify sute test setup
Signed-off-by: Danil-Grigorev <danil.grigorev@suse.com>
* Define secrets keys via env for crust-gather exclusion
Use any `SECRET_` prefixed env variable with \n separated content with
environment variable names to exclude from logs collection.
Signed-off-by: Danil-Grigorev <danil.grigorev@suse.com>
* Process e2eConfig individually to populate environment in test
Signed-off-by: Danil-Grigorev <danil.grigorev@suse.com>
* Add documentation for new vars and SECRET_KEYS processing
Signed-off-by: Danil-Grigorev <danil.grigorev@suse.com>
* Use GinkgoWriter for logging in e2e
Replace all usages of fmt.Printf, which skew the log output in parallel
test execution.
Signed-off-by: Danil-Grigorev <danil.grigorev@suse.com>
---------
Signed-off-by: Danil-Grigorev <danil.grigorev@suse.com>
- Re-implement Apply method in local framework
- Add controller names, where needed
- Integration test: init controllers only once per all test cases
Signed-off-by: Danil-Grigorev <danil.grigorev@suse.com>
WIP: Evaluating CreateOrUpdate
Signed-off-by: Danil-Grigorev <danil.grigorev@suse.com>
* Use E2E config instead of ginkgo flags
Signed-off-by: Alexandr Demicev <alexandr.demicev@suse.com>
* Add documentation for public E2E structures and functions
Signed-off-by: Alexandr Demicev <alexandr.demicev@suse.com>
* Use rancher turtles version from the config file
Signed-off-by: Alexandr Demicev <alexandr.demicev@suse.com>
* Update README with information about new config options
Signed-off-by: Alexandr Demicev <alexandr.demicev@suse.com>
---------
Signed-off-by: Alexandr Demicev <alexandr.demicev@suse.com>
* feat: changing to use EKS for management cluster
This change introduces the following changes to the e2e tests:
- For the **full** tests the option to use EKS as a management cluster.
This enabled use an AWS ELB instead on ngrok.
- Changed tests so they are either short, full, local....but not both.
- Increased the Rancher version to v2.8.1
- Added a Rancher restart after installing Rancher Turtles to workaround
and issue with the CRDs being watched.
Signed-off-by: Richard Case <richard.case@suse.com>
* wip: update for other test suites
Signed-off-by: Richard Case <richard.case@suse.com>
* wip: added gitea remove
Signed-off-by: Richard Case <richard.case@suse.com>
---------
Signed-off-by: Richard Case <richard.case@suse.com>
This change adds a new e2e test suite that checks that installing
Rancher Turtles doesn't break v2prov.
The test will provision a RKE2 cluster in Azure. It will then connect to
the cluster via the kubeconfig.
Signed-off-by: Richard Case <richard.case@suse.com>
This change splits the e2e tests into separate suites. Each of which can
have their own cluster setup. This also invloved extracting the
management cluster setup into its own package.
A new test suite will be introduced later to test v2prov.
Signed-off-by: Richard Case <richard.case@suse.com>
This change refactors the existing e2e tests so that there is a new spec
that can be re-used with different template files to enable us to test
different provider combinations.
Additionally the tests have been changed to use an in-cluster Git server
(gitea) so that we can create new repos as part of the test and remove
the reliance on the samples repo.
Signed-off-by: Richard Case <richard.case@suse.com>
yiannistri