mirror of
https://github.com/siderolabs/talos.git
synced 2025-10-27 14:31:11 +01:00
0afd0f651b
Integration test can optionally consume cluster state as generated by the call to `osctl cluster create` and use it to discover nodes in integration tests. This means that now CLI tests can use that as discovery source, and API/K8s tests by default as well. Flat list of nodes is to be replaced by something more complex in the next iteration, but it's good for this PR. As a demo, add CLI test with multiple nodes (dmesg). Signed-off-by: Andrey Smirnov <smirnov.andrey@gmail.com>
28 lines
530 B
Bash
Executable File
28 lines
530 B
Bash
Executable File
#!/bin/bash
|
|
|
|
set -eou pipefail
|
|
|
|
source ./hack/test/e2e.sh
|
|
|
|
PROVISIONER=firecracker
|
|
CLUSTER_NAME=e2e-${PROVISIONER}
|
|
|
|
function create_cluster {
|
|
"${OSCTL}" cluster create \
|
|
--provisioner "${PROVISIONER}" \
|
|
--name "${CLUSTER_NAME}" \
|
|
--masters=3 \
|
|
--mtu 1500 \
|
|
--memory 2048 \
|
|
--cpus 2.0 \
|
|
--cidr 172.20.0.0/24 \
|
|
--init-node-as-endpoint \
|
|
--wait \
|
|
--install-image docker.io/autonomy/installer:latest
|
|
}
|
|
|
|
create_cluster
|
|
get_kubeconfig
|
|
run_talos_integration_test
|
|
run_kubernetes_integration_test
|