Use k3s in pipeline 52/142052/69
authorFiete Ostkamp <fiete.ostkamp@telekom.de>
Mon, 15 Sep 2025 13:55:13 +0000 (15:55 +0200)
committerFiete Ostkamp <fiete.ostkamp@telekom.de>
Thu, 18 Sep 2025 10:36:19 +0000 (12:36 +0200)
commit9f9f50031c10407d9f46623e52d504c11c411440
tree4d2f5a6b0530914c5027649a30fb228f3d325111
parent59fe7c6c1eb7d3eb12e03924acce84e7a6153df8
Use k3s in pipeline

- replace kubespray with k3s which is
- much simpler to set up + does not need
  to be 'production-ready' to test
  deployment in pipeline
- disable addon installation
- enable k8s-plugin test run by verify-shell
- do not enable the other plugin_ tests since that
  would be too much for this CR
- pull docker images through nexus proxy to
  avoid rate limiting from dockerhub
- bump snapshot version to 0.10.2-SNAPSHOT

Issue-ID: MULTICLOUD-1513
Change-Id: I8ca40dff67ddf41153bdd2f7cfa07a22fb2b03f5
Signed-off-by: Fiete Ostkamp <fiete.ostkamp@telekom.de>
22 files changed:
build/Dockerfile
deployments/Dockerfile
deployments/_functions.sh
deployments/build.sh
deployments/docker-compose.yml
docs/kud_architecture.rst
kud/hosting_providers/vagrant/installer.sh
kud/tests/_common_test.sh
kud/tests/_functions.sh
kud/tests/emco.sh
kud/tests/negative_tests/_test_functions.sh
kud/tests/negative_tests/_test_variables_setup.sh
kud/tests/plugin.sh
kud/tests/plugin_collection_v2.sh
kud/tests/plugin_eaa.sh
kud/tests/plugin_edgex.sh
kud/tests/plugin_fw.sh
kud/tests/plugin_ncm_v2.sh
src/k8splugin/Makefile
src/k8splugin/go.mod
src/k8splugin/go.sum
src/orchestrator/scripts/docker-compose.yml