Functions Virtualization requirements. Raspberry PI is also supported to verify
datacenters as the lowest cost (50 euros hardware and software included).
-| Functest releases | Kubernetes releases |
-|-------------------|---------------------------|
-| Hunter | v1.13 |
-| Iruya | v1.15 |
-| Jerma | v1.17 |
-| Kali | v1.19 |
-| Leguer | v1.20 |
-| Master | v1.21.0-alpha.3 (rolling) |
+| Functest releases | Kubernetes releases |
+|-------------------|-------------------------------|
+| Hunter | v1.13 |
+| Iruya | v1.15 |
+| Jerma | v1.17 |
+| Kali | v1.19 |
+| Leguer | v1.20 |
+| **Master** | **v1.21.0-alpha.3 (rolling)** |
## Prepare your environment
| cnf_conformance | functest | cnf | 02:00 | PASS |
+-------------------------+------------------+--------------+------------------+----------------+
```
+
+
+## Use on air gap environments (no access to Internet)
+
+To test a Kubernetes without access to Internet, repository mirrors needs to be
+provided.
+
+Currently, all tests supports this feature except cnf conformance.
+
+There's two ways for providing the repository mirrors:
+
+- Give an environment variable (`MIRROR_REPO`) which gives a repository with
+ all needed images.
+- Gives an environment variable per needed repo:
+ - `DOCKERHUB_REPO` for DockerHub repository (`docker.io`)
+ - `GCR_REPO` for Google Cloud repository (`gcr.io`)
+ - `K8S_GCR_REPO` for Kubernetes repository (`k8s.gcr.io`)
+ - `QUAY_REPO` for Quay repository (`quay.io`)
+
+All needed images are given in
+[functest-kubernetes/ci/images.txt](functest-kubernetes/ci/images.txt)
+
+For e2e tests, `docker.io` is hardcoded. it does mean that you'll have to set up
+a mirror on docker. An example on how to set it up on docker daemon is provided
+here:
+[daemon-configuration-file](
+https://docs.docker.com/engine/reference/commandline/dockerd/#daemon-configuration-file)