mirror of
https://github.com/kata-containers/kata-containers.git
synced 2025-11-13 00:53:04 +00:00
11e0099fb5
The first part of simplifying things to have all our tests using GitHub actions is moving the k8s tests to this repo, as those will be the first vict^W targets to be migrated to GitHub actions. Those tests have been slightly adapted, mainly related to what they load / import, so they are more self-contained and do not require us bringing a lot of scripts from the tests repo here. A few scripts were also dropped along the way, as we no longer plan to deploy kubernetes as part of every single run, but rather assume there will always be k8s running whenever we land to run those tests. It's important to mention that a few tests were not added here: * k8s-block-volume: * k8s-file-volume: * k8s-volume: * k8s-ro-volume: These tests depend on some sort of volume being created on the kubernetes node where the test will run, and this won't fly as the tests will run from a GitHub runner, targetting a different machine where kubernetes will be running. * https://github.com/kata-containers/kata-containers/issues/6566 * k8s-hugepages: This test depends a whole lot on the host where it lands and right now we cannot assume anything about that anymore, as the tests will run from a GitHub runner, targetting a different machine where kubernetes will be running. * https://github.com/kata-containers/kata-containers/issues/6567 * k8s-expose-ip: This is simply hanging when running on AKS and has to be debugged in order to figure out the root cause of that, and then adapted to also work on AKS. * https://github.com/kata-containers/kata-containers/issues/6578 Till those issues are solved, we'll keep running a jenkins job with hose tests to avoid any possible regression. Last but not least, I've decided to **not** keep the history when bringing those tests here, otherwise we'd end up polluting a lot the history of this repo, without any clear benefit on doing so. Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>
39 lines
1.3 KiB
Bash
39 lines
1.3 KiB
Bash
#
|
|
# Copyright (c) 2021 Red Hat, Inc.
|
|
#
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
#
|
|
# This script is evoked within an OpenShift Build to product the binary image,
|
|
# which will contain the Kata Containers installation into a given destination
|
|
# directory.
|
|
#
|
|
# This contains variables and functions common to all e2e tests.
|
|
|
|
# Variables used by the kubernetes tests
|
|
export docker_images_nginx_version="1.15-alpine"
|
|
export container_images_agnhost_name="k8s.gcr.io/e2e-test-images/agnhost"
|
|
export container_images_agnhost_version="2.21"
|
|
|
|
# Timeout options, mainly for use with waitForProcess(). Use them unless the
|
|
# operation needs to wait longer.
|
|
wait_time=90
|
|
sleep_time=3
|
|
|
|
# Timeout for use with `kubectl wait`, unless it needs to wait longer.
|
|
# Note: try to keep timeout and wait_time equal.
|
|
timeout=90s
|
|
|
|
# issues that can't test yet.
|
|
fc_limitations="https://github.com/kata-containers/documentation/issues/351"
|
|
|
|
# Path to the kubeconfig file which is used by kubectl and other tools.
|
|
# Note: the init script sets that variable but if you want to run the tests in
|
|
# your own provisioned cluster and you know what you are doing then you should
|
|
# overwrite it.
|
|
export KUBECONFIG="${KUBECONFIG:-$HOME/.kube/config}"
|
|
|
|
get_pod_config_dir() {
|
|
pod_config_dir="${BATS_TEST_DIRNAME}/runtimeclass_workloads"
|
|
info "k8s configured to use runtimeclass"
|
|
}
|