chore(helm): removing depricated docs
This commit is contained in:
parent
b2bedd3923
commit
a74f6bdfbe
2 changed files with 0 additions and 80 deletions
|
|
@ -1,33 +0,0 @@
|
|||
### Installing OpenReplay on any VM (Debian based, preferably Ubuntu 20.04)
|
||||
|
||||
You can start testing OpenReplay by installing it on any VM (at least `2 vCPUs, 8 GB of RAM and 50 GB of storage`). We'll initialize a single node kubernetes cluster with [k3s](https://k3s.io) and install OpenReplay on the cluster.
|
||||
|
||||
```bash
|
||||
cd helm && bash install.sh
|
||||
```
|
||||
|
||||
### Installing OpenReplay on Kubernetes
|
||||
|
||||
OpenReplay runs 100% on kubernetes. So if you've got a kubernetes cluster, preferably, a cluster dedicated to OpenReplay (on a single node of `4 vCPUs, 8 GB of RAM and 50 GB of storage`). You can run the script, which internally uses helm to install OpenReplay.
|
||||
|
||||
We hope your cluster has provision to create a [service type](https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer) `LoadBalancer` for exposing OpenReplay on the internet.
|
||||
|
||||
```bash
|
||||
cd helm && bash kube-install.sh
|
||||
```
|
||||
|
||||
### OpenReplay CLI
|
||||
|
||||
The CLI is helpful for managing basic aspects of your OpenReplay instance, things such as restarting or reinstalling a service, accessing a component's logs or simply checking the status of your backend services. Below the list of covered operations:
|
||||
|
||||
- status: status of the running services
|
||||
- logs: logs of a specific service
|
||||
- stop: stop one or all services
|
||||
- start: start one or all services
|
||||
- restart: restart one or all services
|
||||
|
||||
For more information:
|
||||
|
||||
```bash
|
||||
cd helm && openreplay-cli -h
|
||||
```
|
||||
|
|
@ -1,47 +0,0 @@
|
|||
## Helm charts for installing OpenReplay components
|
||||
|
||||
Installation components are separated by namespaces.
|
||||
|
||||
**Namespace:**
|
||||
|
||||
- **app:** Core OpenReplay application related components.
|
||||
- alerts
|
||||
- utilities
|
||||
- assets
|
||||
- chalice
|
||||
- ender
|
||||
- sink
|
||||
- storage
|
||||
- http
|
||||
- integrations
|
||||
- db
|
||||
|
||||
- **db:** Contains following databases and backend components.
|
||||
- kafka (ee)
|
||||
- redis
|
||||
- postgresql
|
||||
- clickhouse (ee)
|
||||
- minio
|
||||
- nfs-server
|
||||
|
||||
- **longhorn:** Storage solution for kubernetes PVs.
|
||||
|
||||
- **nginx-ingress:** Nginx ingress for internet traffic to enter the kubernetes cluster.
|
||||
|
||||
**Scripts:**
|
||||
- **install.sh**
|
||||
|
||||
Installs OpenReplay in a single node machine.
|
||||
|
||||
This script is a wrapper around the `install.sh` with [k3s](https://k3s.io/) as kubernetes distro.
|
||||
|
||||
Note: As of now this script support only Ubuntu, as we've to install some packages to enable `NFS`.
|
||||
|
||||
- **kube-install.sh:**
|
||||
|
||||
Installs OpenReplay on any given kubernetes cluster. Has 3 configuration types:
|
||||
- small (2cores 8G RAM)
|
||||
- medium (4cores 16G RAM)
|
||||
- recommended (8cores 32G RAM)
|
||||
|
||||
For all options, `bash kube-install.sh -h`
|
||||
Loading…
Add table
Reference in a new issue