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
Copy file name to clipboardExpand all lines: docs/next/modules/en/pages/operator/certificationsuite.adoc
+5-3
Original file line number
Diff line number
Diff line change
@@ -64,9 +64,11 @@ In previous sections we introduced the main actions performed in the sample test
64
64
* The main test suite, and the one used as an example, is based on a GitOps flow and uses https://github.com/rancher/fleet[Fleet] as a GitOps orchestrator tool. Based on the cluster templates provided (you can check the ones that come with the example integration https://github.com/rancher-sandbox/turtles-integration-suite-example/tree/main/suites/data/cluster-templates[here]), it will create the CAPI clusters defined in the YAML files. Once this/these cluster/s are available, they will be configured to be xref:../tutorials/first-cluster.adoc[imported into Rancher using Turtles] and it will verify that the downstream cluster/s is/are accessible via Rancher. It will also check that deletion can be performed on downstream clusters and that they are no longer available in Rancher.
65
65
66
66
== Other options
67
+
:kubernetes-version: v1.31.4
67
68
68
69
You can take a look at the `config.yaml` https://github.com/rancher-sandbox/turtles-integration-suite-example/blob/main/config/config.yaml[file] in the `turtles-integration-suite-example` repository, which contains a list of environment variables used during test environment deployment and test execution. The following is a truncated version of the above mentioned YAML file:
69
70
71
+
[source,yaml,subs=attributes+]
70
72
----
71
73
...
72
74
variables:
@@ -76,10 +78,10 @@ variables:
76
78
ARTIFACTS_FOLDER: "_artifacts"
77
79
MANAGEMENT_CLUSTER_ENVIRONMENT: "kind" # supported options are eks, isolated-kind, kind
0 commit comments