3293317c40
This PR Adds notes and example on logging for Ray/K8s. Implements an API Reference paging pointing to the configuration guide and the RayCluster CR definition. Takes managed K8s services out of the tabbed structure, to make that page look less sad. Adds a comparison of the KubeRay operator and legacy K8s operator Adds an architecture diagram for the autoscaling sections Fixes some other minor items Adds some info about networking to the configuration guide, removes the previously planned networking page Signed-off-by: Dmitri Gekhtman <dmitri.m.gekhtman@gmail.com>
2.2 KiB
(kuberay-k8s-setup)=
Managed Kubernetes services
The KubeRay operator and Ray can run on any cloud or on-prem Kubernetes cluster. The simplest way to provision a remote Kubernetes cluster is to use a cloud-based managed service. We collect a few helpful links for users who are getting started with a managed Kubernetes service.
(gke-setup)=
Setting up a GKE cluster (Google Cloud)
You can find the landing page for GKE here. If you have an account set up, you can immediately start experimenting with Kubernetes clusters in the provider's console. Alternatively, check out the documentation and quickstart guides. To successfully deploy Ray on Kubernetes, you will need to configure pools of Kubernetes nodes; find guidance here.
(eks-setup)=
Setting up an EKS cluster (AWS)
You can find the landing page for EKS here. If you have an account set up, you can immediately start experimenting with Kubernetes clusters in the provider's console. Alternatively, check out the documentation and quickstart guides. To successfully deploy Ray on Kubernetes, you will need to configure groups of Kubernetes nodes; find guidance here.
(aks-setup)=
Setting up an AKS (Microsoft Azure)
You can find the landing page for AKS here. If you have an account set up, you can immediately start experimenting with Kubernetes clusters in the provider's console. Alternatively, check out the documentation and quickstart guides. To successfully deploy Ray on Kubernetes, you will need to configure pools of Kubernetes nodes; find guidance here.