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
ingress_domain="example.com" # Default None, Mandatory for Vanilla Kubernetes Clusters - ingress_domain is ignored on OpenShift Clusters as a route is created.
26
+
local_interactive=False, # Default False
26
27
))
27
28
```
29
+
Note: On OpenShift, the `ingress_domain` is only required when `local_interactive` is enabled. - This may change soon.
28
30
29
31
Upon creating a cluster configuration with `mcad=True` an appwrapper will be created featuring the Ray Cluster and any Routes, Ingresses or Secrets that are needed to be created along side it.<br>
30
32
From there a user can call `cluster.up()` and `cluster.down()` to create and remove the appwrapper thus creating and removing the Ray Cluster.
@@ -36,7 +38,7 @@ The Ray Cluster and service will be created by KubeRay directly and the other co
36
38
To create a Ray Cluster using the CodeFlare SDK in a Vanilla Kubernetes environment an `ingress_domain` must be passed in the Cluster Configuration.
37
39
This is used for the creation of the Ray Dashboard and Client ingresses.
38
40
39
-
`ingress_options` can be passed to create a custom Ray Dashboard ingress, `ingress_domain` is still a required variable for the Client ingress.
41
+
`ingress_options` can be passed to create a custom Ray Dashboard ingress, `ingress_domain` is still a required variable for the Client route/ingress.
40
42
An example of `ingress_options` would look like this.
// This test covers the Ray Cluster creation authentication functionality of openshift_oauth without login and assert the warning only authorised users can submit jobs
33
+
// This test covers the Ray Cluster creation authentication functionality of openshift_oauth without login and assert the Unauthorized 403 error
0 commit comments