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: README.md
+12-11Lines changed: 12 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -33,8 +33,6 @@ The e2e tests can be executed locally by running the following commands:
33
33
```bash
34
34
# Create a KinD cluster
35
35
make kind-e2e
36
-
# Deploy Kueue
37
-
make kueue-e2e
38
36
# Install the CRDs
39
37
make install
40
38
```
@@ -43,20 +41,15 @@ The e2e tests can be executed locally by running the following commands:
43
41
Some e2e tests cover the access to services via Ingresses, as end-users would do, which requires access to the Ingress controller load balancer by its IP.
44
42
For it to work on macOS, this requires installing [docker-mac-net-connect](https://github.com/chipmk/docker-mac-net-connect).
45
43
46
-
2. Start the operator locally:
47
-
48
-
```bash
49
-
NAMESPACE=default make run
50
-
```
51
-
52
-
Alternatively, You can run the operator from your IDE / debugger.
53
-
54
-
3. Set up the test CodeFlare stack:
44
+
2. Setup the rest of the CodeFlare stack.
55
45
56
46
```bash
57
47
make setup-e2e
58
48
```
59
49
50
+
[!NOTE]
51
+
Kueue will only activate its Ray integration if KubeRay is installed before Kueue (as done by this make target).
52
+
60
53
[!NOTE]
61
54
In OpenShift the KubeRay operator pod gets random user assigned. This user is then used to run Ray cluster.
62
55
However the random user assigned by OpenShift doesn't have rights to store dataset downloaded as part of test execution, causing tests to fail.
@@ -76,6 +69,14 @@ The e2e tests can be executed locally by running the following commands:
0 commit comments