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
image="quay.io/project-codeflare/ray:latest-py39-cu118", # Mandatory Field
23
23
instascale=False, # Default False
24
24
machine_types=["m5.xlarge", "g4dn.xlarge"],
25
-
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
27
25
))
28
26
```
29
-
Note: On OpenShift, the `ingress_domain` is only required when `local_interactive` is enabled. - This may change soon.
30
27
31
28
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>
32
29
From there a user can call `cluster.up()` and `cluster.down()` to create and remove the appwrapper thus creating and removing the Ray Cluster.
33
30
34
31
In cases where `mcad=False` a yaml file will be created with the individual Ray Cluster, Route/Ingress and Secret included.<br>
35
32
The Ray Cluster and service will be created by KubeRay directly and the other components will be individually created.
36
-
37
-
## Ray Cluster Configuration in a Vanilla Kubernetes environment (Non-OpenShift)
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.
39
-
This is used for the creation of the Ray Dashboard and Client ingresses.
40
-
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.
42
-
An example of `ingress_options` would look like this.
0 commit comments