Install and upgrade

1. Introduction

This chart bootstraps a replication cluster deployment on a cluster using the package manager.

application charts can be used with for deployment and management of Helm Charts in clusters.

Prerequisites

Kubernetes 1.23+
Helm 3.8.0+
PV provisioner support in the underlying infrastructure

2. Obtain the kubeconfig file

Download the kubeconfig certificate from K8S and associate your account to ensure the following permissions：

 - configmap:*
 - pv:*
 - pvc:*
 - service:*
 - deployment:*
 - ns: create, get, list, watch
 - events: create, get, list,delete, watch
 - secret: *

3. Create the `apitable-ee.yaml` ,file and modify the custom configuration

Note: Use the application service image as per the actual scenario. Make sure to enter the correct license key below to execute the one-click deployment.

license: "<replace-your-license>"

global:
  # replace your storage class
  defaultStorageClass: ""
  env:
    EDITION: "apitable-saas"
    MYSQL_DATABASE: "apitable"
    MYSQL_PASSWORD: "apitable@com"
    MYSQL_USERNAME: "root"
    MYSQL_PORT: "3306"
    MYSQL_HOST: "mysql-primary"
    DATABASE_TABLE_PREFIX: "apitable_"
    RABBITMQ_HOST: rabbitmq
    RABBITMQ_PASSWORD: 7r4HVvsrwP4kQjAgj8Jj
    RABBITMQ_PORT: "5672"
    RABBITMQ_USERNAME: user
    RABBITMQ_VHOST: /
    REDIS_DB: "4"
    REDIS_HOST: redis-master
    REDIS_PASSWORD: UHWCWiuUMVyupqmW4cXV
    REDIS_PORT: "6379"

images:
  registry: ghcr.io
  username: ""
  password: ""
  app:
    backend_server: v1.13.0-release.17_build7871
    databus_server: v1.13.0-release.19_build2415
    fusion_server: v1.13.0-release.19_build10113
    imageproxy_server: v0.13.4-alpha_build13
    nest_rest_server: v1.13.0-release.19_build10113
    room_server: v1.13.0-release.19_build10113
    web_server: v1.13.0-op_build9066
    init_appdata: v1.13.0-alpha_build259
    init_db: v1.13.0-release.19_build1556
    init_settings: v1.9.0-alpha_build3807
  repository:
    common: apitable/ee
    app:
      init_appdata: apitable/apitable-ee
      init_settings: apitable/apitable-ee
      openresty: apitable/openresty
# full image format:  ghcr.io/apitable/ee/backend-server:v1.13.0-release.17_build7871

app:
  room_server:
    env:
      ROBOT_OFFICIAL_SERVICE_SLUG: "apitable"
  nest_rest_server:
    env:
      ROBOT_OFFICIAL_SERVICE_SLUG: "apitable"

4. One-click installation and upgrade.

To install the chart with the release name apitable-release:

helm upgrade --install apitable-release -f apitable-ee.yaml oci://registry-1.docker.io/vikadata/vika-helm-chart -n apitable-app

Note: You need to substitute the placeholders REGISTRY_NAME and REPOSITORY_NAME with a reference to your Helm chart registry and repository.

These commands deploy apitable on the Kubernetes cluster in the default configuration. The section lists the parameters that can be configured during installation.

Tip: List all releases using helm list

To upgrade:

helm upgrade --install apitable-release -f apitable-ee.yaml oci://registry-1.docker.io/vikadata/vika-helm-chart -n apitable-app

To uninstall: