Skip to content

Latest commit

 

History

History
59 lines (36 loc) · 1.75 KB

conformance-tests.md

File metadata and controls

59 lines (36 loc) · 1.75 KB
Raw

Kubernetes Conformance Tests

The conformance test checks that a kubernetes installation supports a minimum required feature set.

Kubernetes Cluster

You will need to have a cluster already running, and a kubeconfig with the current-context set to the cluster you wish to test.

Make sure only the essential pods are running, and there are no failed or pending pods. If you are testing a small / development cluster, you may need to increase the node memory or tests could inconsistently fail (e.g. 2048mb for single-node vagrant).

Clone Kubernetes

git clone https://github.com/kubernetes/kubernetes.git

Checkout Conformance Test branch

cd kubernetes
git checkout conformance-test-v1

Create Kubernetes Binaries

make clean
make quick-release

Set Worker Count

Modify the WORKERS count to match the deployment you are testing.

WORKERS=1; sed -i '' "s/NUM_MINIONS=[0-9]/NUM_MINIONS=${WORKERS}/" hack/conformance-test.sh

Run Conformance Tests

The command below expects a kubeconfig with the current context set to the cluster you wish to test. To set the path, update KUBECONFIG in the command below.

KUBECONFIG=$HOME/.kube/config hack/conformance-test.sh 2>&1 | tee conformance.$(date +%FT%T%z).log

Expected Test Case Failures

Either due to single-node installations, or installation default settings, a couple tests are expected to fail:

Single Node

  • should proxy to cadvisor: We disable cadvisor from listening on all interfaces: --cadvisor-port=0
  • should function for intra-pod communication: Single node installation has no additional workers to communicate with.

Multi Node

  • should proxy to cadvisor: We disable cadvisor from listening on all interfaces: --cadvisor-port=0