constellation/conformance
datosh 2a766a3ab5 Feat/conformity test (#79)
* Added files required to request conformance with kubernetes
* Extended firewall implementation to allow port ranges
* Added default nodeport range to vpc network config
2022-04-26 17:09:03 +02:00
..
.gitignore Feat/conformity test (#79) 2022-04-26 17:09:03 +02:00
PRODUCT.yml Feat/conformity test (#79) 2022-04-26 17:09:03 +02:00
README.md Feat/conformity test (#79) 2022-04-26 17:09:03 +02:00

Reproducing Conformance Test Results

Prerequisites

Install & configure gcloud CLI for access to GCP.

Install WireGuard for connecting to your cluster

Install kubectl for working with Kubernetes

For more information follow our documentation.

Additionally, Sonobuoy CLI is required. These tests results were produced using Sonobuoy v0.56.4.

Provision Constellation Cluster

constellation create gcp 1 2 n2d-standard-2 -y
constellation init
wg-quick up ./wg0.conf
export KUBECONFIG="$PWD/constellation-admin.conf"

Run Conformance Tests

# Runs for ~2 hours.
sonobuoy run --mode certified-conformance
# Once status shows tests have completed...
sonobuoy status
# ... download & display results.
outfile=$(sonobuoy retrieve)
sonobuoy results $outfile

Fetch Test Log & Report

The provided e2e.log & junit_01.xml were fetched like this:

tar -xvf $outfile
cat plugins/e2e/results/global/e2e.log
cat plugins/e2e/results/global/junit_01.xml

Cleanup

# Remove test deployments
sonobuoy delete --wait
# Or, shutdown cluster
wg-quick down ./wg0.conf
./constellation terminate
rm constellation-mastersecret.base64