From cc1651f6195365c9d187f59c2545851a877e943e Mon Sep 17 00:00:00 2001 From: Konradas Bunikis Date: Wed, 11 Sep 2024 13:36:31 +0300 Subject: [PATCH] docs: Add initial FAQ page (#165) --- docs/faq.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/faq.md b/docs/faq.md index 318b08d..314c971 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -1 +1,17 @@ # Frequently Asked Questions + +## How does Fireactions compare to other solutions? + +Self hosted GitHub runners are a great way to run your CI/CD jobs on your own infrastructure. However, setting up and managing self-hosted runners can be a complex and time-consuming process. Fireactions aims to simplify this process by providing a lightweight and secure solution for orchestrating self-hosted GitHub runners. + +Compared to [ARC(Actions Runner Controller)](https://github.com/actions/actions-runner-controller), ARC is a Kubernetes operator with primary use case of managing self-hosted GitHub runners in Kubernetes clusters, while Fireactions is a standalone application that can be run on any regular bare metal server or a VM that supports nested virtualization. + +Kubernetes can be an overkill for most situations and managing a Kubernetes cluster can be complex and resource intensive task. + +## Do I need to use a bare metal server or a VM to run Fireactions? + +Fireactions can be run on any regular bare metal server or a VM that supports nested virtualization. Do note that running Fireactions on a VM might have performance implications, especially if you are running multiple concurrent jobs. + +## Is there GPU support in Fireactions? + +Currently, Fireactions **does not support GPU workloads**. However, we are considering on adding support in the future.