You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: test/README.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ Please note that `docker` needs to be installed in order for this script to succ
40
40
As part of these tests, we attempt pulling and scanning an image hosted on a private GCR registry. For this test case to work, one has to define the following environment variables: `GCR_IO_SERVICE_ACCOUNT`, `GCR_IO_DOCKERCFG`.
41
41
42
42
Our integration tests may use different Kubernetes platforms to host the Kubernetes-Monitor. These platforms may use an existing cluster, or create a new one. Both decisions are based on the environment variables:
43
-
*`TEST_PLATFORM` (`kind`, `eks`)
43
+
*`TEST_PLATFORM` (`kind`, `kindolm`, `eks`)
44
44
*`CREATE_CLUSTER` (`true`, `false`).
45
45
46
46
Additionally, the deployment of the Kubernetes-Monitor can be configured through an environment variable:
@@ -83,6 +83,14 @@ This test runs whenever we commit to our `staging` branch, and at the moment may
83
83
84
84
Run with `npm run test:integration:openshift4`.
85
85
86
+
### KinD with OLM ###
87
+
88
+
This test helps us ensure our operator is installable and functioning on a plain k8s cluster.
89
+
90
+
This test runs whenever we commit to any branch.
91
+
92
+
Run with `npm run test:integration:kindolm:operator`.
93
+
86
94
### Package Managers ###
87
95
88
96
These tests attempt to provide some more thorough coverage for our scans of specific package manager: APK, APT and RPM.
0 commit comments