e2e/

README

Requirements

go get -u github.com/giantswarm/e2e-harness

environment variables example

export CLUSTER_NAME="test-e2e"

export AZURE_LOCATION="westeurope"
export COMMON_DOMAIN_RESOURCE_GROUP="godsmack"
export COMMON_DOMAIN_GUEST_NO_K8S="${COMMON_DOMAIN_RESOURCE_GROUP}.${AZURE_LOCATION}.azure.gigantic.io"
export COMMON_DOMAIN_GUEST="k8s.${COMMON_DOMAIN_GUEST_NO_K8S}"

// ssh key to grant access to guest cluster nodes, ssh user is: test-user
export IDRSA_PUB=$(cat ~/.ssh/id_rsa.pub)

export CIRCLE_SHA1="master"

export AZURE_CLIENTID="xxxxxx"
export AZURE_CLIENTSECRET="xxxxxx"
export AZURE_SUBSCRIPTIONID="xxxxxx"
export AZURE_TENANTID="xxxxxx"

export CIRCLE_BUILD_NUM="990"
OR
(
	export AZURE_CIDR="10.42.0.0/16"
	export AZURE_CALICO_SUBNET_CIDR="10.42.128.0/17"
	export AZURE_MASTER_SUBNET_CIDR="10.42.0.0/24"
	export AZURE_WORKER_SUBNET_CIDR="10.42.1.0/24"
)

How to run e2e test

$ minikube start --extra-config=apiserver.Authorization.Mode=RBAC
$ e2e-harness setup --remote=false
$ e2e-harness test --test-dir=e2e/test/mytest

Export node journal logs into Rapid7/Logentries

Exporting logs can be enabled by setting IGNITION_DEBUG_ENABLED: "true" within respective test case in .circleci/config.yml file. Logs can be found in Rapid7 Insight platform under Tenant/Azure log set. Logs prefix has a format "<cluster_id>-<IGNITION_DEBUG_LOGS_PREFIX>-". E.g. fe34t-wip-pr-multiaz-master.

Credentials to Rapid7 Insight can be found in Keepass under Logentries / Rapid7.