openreplay

History

Rajesh Rajendran 61835a76f0 chore(install): creating cache topic Signed-off-by: Rajesh Rajendran <rjshrjndrn@gmail.com>		2021-12-09 17:23:44 +05:30
..
app
db
longhorn
management
monitoring/kube-prometheus-stack
nginx-ingress
roles/openreplay	chore(install): creating cache topic	2021-12-09 17:23:44 +05:30
build_deploy.sh
install.sh
kube-install.sh
local_run.md
migration.yaml
openreplay-cli
README.md
setup.yaml
upgrade.sh	fix(upgrade): if enterprise edition, copy enterprise code. (#244 )	2021-12-08 04:04:05 +00:00
vars.yaml
vars_template.yaml

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 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