Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions examples/v1beta1/fpga/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,9 @@ visit the [InAccel](https://docs.inaccel.com) documentation.
## Simplifying FPGA management in EKS\* (Elastic Kubernetes Service)

\*_For development and testing purposes you can still [deploy Kubeflow Katib
using Minikube](https://kubeflow.org/docs/started/workstation/minikube-linux) in
a single AMI instance. In production environments, Amazon's managed Kubernetes
service ([EKS](https://aws.amazon.com/eks)) is recommended._
using MicroK8s](https://ubuntu.com/tutorials/accelerated-ml-experiments-on-microk8s-with-inaccel-fpga-operator-and-kubeflow-katib)
in a single AMI instance. In production environments, Amazon's managed
Kubernetes service ([EKS](https://aws.amazon.com/eks)) is recommended._

The InAccel FPGA Operator allows administrators of Kubernetes clusters to manage
FPGA nodes just like CPU nodes in the cluster. Instead of provisioning a special
Expand All @@ -37,7 +37,7 @@ Kubernetes, as a Helm app on your cluster, with the following command.
```sh
helm repo add inaccel https://setup.inaccel.com/helm

helm install inaccel inaccel/fpga-operator
helm install -n kube-system inaccel inaccel/fpga-operator
```

You can verify that your nodes have available FPGAs with the following command:
Expand Down