Kubernetes
Kubernetes (K8s) is an open source platform for managing, scaling, and automating the deployment of containerized applications. It's one of the most popular container orchestration tools. This guide helps you to install Appsmith on a Kubernetes cluster using the Helm package manager.
Prerequisites
Before you install Appsmith, ensure the following are installed:
Helm Package Manager - This is a package manager for Kubernetes clusters. It allows you to install and manage applications on Kubernetes clusters. To install Helm, follow the instructions for your platform from the official Helm documentation.
kubectl
- This is the command-line interface to manage resources on Kubernetes clusters. To installkubectl
, follow the instructions for your platform from the official Kubernetes documentation.
Configure Kubernetes cluster
Follow one of the available guidelines below to configure the Kubernetes cluster.
- AWS EKS
- Minikube
- Google Cloud Kubernetes
- Microk8s
- Set up the Kubernetes cluster by creating a kubeconfig for Amazon EKS.
- Ensure that you have a default storage class running. If not, create default storage class
- The NGINX Ingress Controller is enabled by default. If not, install NGINX Controller for AWS EKS. Ensure that you enable the correct version for your cluster.
- Setup kubectl
- Ensure that you have a default storage class running. If not, enable addon default-storage class
- The NGINX Ingress Controller is enabled by default. If not, set up Ingress on Minikube with the NGINX Ingress Controller. Ensure that you enable the correct version for your cluster.
- Configure cluster access for kubectl on Google Cloud Kubernetes.
- Ensure that you have a default storage class running. If not, set up a default storage class on Google Kubernetes Engine[GKE].
- The NGINX Ingress Controller is enabled by default. If not, install ingress controller on Google Kubernetes Engine[GKE]. Ensure that you enable the correct version for your cluster.
- Set up Kubernetes by following working with kubectl.
- Ensure that you have a default storage class running. If not, enable storage class.
- The NGINX Ingress Controller is enabled by default. If not, add on: Ingress. Ensure that you enable the correct version for your cluster.
Install Appsmith
You've installed and configured the Kubernetes cluster. Great, now go ahead and install Appsmith using Helm.
- Community Edition
- Business Edition
Follow the steps below to install Appsmith on your Kubernetes cluster:
Download the
values.yaml
file, and place it into the Appsmith installation folder. Or, run the followingcURL
command:curl -L https://bit.ly/3ETEgPT -o "$PWD/values.yml"
Add the Appsmith chart repository with:
helm repo add appsmith https://helm.appsmith.com
Load the Appsmith chart repository with:
helm repo update
Install Appsmith on your Kubernetes cluster using the Helm chart. Replace
<your-namespace>
with the namespace you want to install Appsmith in:helm install appsmith appsmith/appsmith --namespace <your-namespace>
When installing Appsmith using Helm, it automatically creates all the necessary Kubernetes objects to run the app on your clusters, such as pods, services, and ingresses with the default configuration. For more information on customizing the configuration, checkout the Configure Appsmith section.
Verify the status of the Appsmith installation by running the following command:
kubectl -n <your-namespace> rollout status deployment <release-name>-appsmith
When the deployment is ready, a message that indicates the deployment of "appsmith" has been successfully rolled out is displayed.
Access Appsmith by visiting the URL that was output by the Helm installation command. Use the
kubectl
command to get the URL. The URL has ahostname
andport
of the Appsmith ingress to access Appsmith using a web browser.kubectl -n <your-namespace> get ingress <release-name>-appsmith
Congratulations, you have successfully installed Appsmith on your Kubernetes cluster using Helm. For more detailed instructions and options for configuring the Appsmith Helm chart, see the Configure Appsmith section below.
Configure Appsmith
The Appsmith installation works with the default configuration, but you also have the option to customize it to fit your specific needs. To configure the installation parameters, it's recommended to use the values.yaml
file. This file allows you to specify the settings and options you want to use for your Appsmith installation, allowing you to tailor the installation to your needs. The following is a comprehensive list of available parameters.
Parameters
Customize Appsmith by using either Helm parameters or Appsmith-specific parameters. The table below provides details on the various Helm and Appsmith parameters that are available for configuration.
Global
Name | Description | Value |
---|---|---|
global.namespaceOverride | Override the namespace for resource deployed by the chart | "" |
global.storageClass | Global StorageClass for Persistent Volume | "" |
Common
Name | Description | Value |
---|---|---|
fullnameOverride | String to fully override appsmith.name template | "" |
containerName | Specify container's name running in the pods | "appsmith" |
commonLabels | Labels to add to all deployed objects | {} |
commonAnnotations | Annotations to add to all deployed objects | {} |
Appsmith image
Name | Description | Value |
---|---|---|
image.registry | Appsmith image registry | index.docker.io |
image.repository | Appsmith image repository | appsmith/appsmith-editor |
image.tag | Appsmith image tag | latest |
image.pullPolicy | Appsmith image pull policy | IfNotPresent |
Appsmith deployment
Name | Description | Value |
---|---|---|
strategyType | Appsmith deployment strategy type | RollingUpdate |
schedulerName | Alternate scheduler | "" |
podAnnotations | Annotations for Appsmith pods | {} |
podSecurityContext | Appsmith pods security context | {} |
securityContext | Set security context | {} |
resources.limits | The resources limits for the Appsmith container | {} |
resources.requests | The requested resources for the Appsmith container | {} |
nodeSelector | Node labels for pod assignment | {} |
tolerations | Tolerations for pod assignment | [] |
affinity | Affinity fod pod assignment | {} |
Appsmith namespace
Name | Description | Value |
---|---|---|
namespace.create | Enable creation of Namespace | true |
Appsmith service account
Name | Description | Value |
---|---|---|
serviceAccount.create | Enable creation of ServiceAccount for Appsmith pods | true |
serviceAccount.name | Name of the created ServiceAccount . If not set, a name is generated using the appsmith.fullname template | "" |
serviceAccount.annotations | Additional service account annotations | {} |
Traffic exposure
Name | Description | Value |
---|---|---|
service.type | Appsmith service type | ClusterIP |
service.port | Appsmith service port | 80 |
service.portName | Appsmith service port name | appsmith |
service.nodePort | Appsmith service node port to expose to expose | 8000 |
service.clusterIP | Appsmith service Cluster | "" |
service.loadBalancerIP | Appsmith service Load Balancer IP | "" |
service.loadBalancerSourceRanges | Appsmith service Load Balancer sources | [] |
service.annotations | Additional custom annotations for Appsmith service | {} |
ingress.enabled | Enable ingress record generation for Appsmith | false |
ingress.hosts | An array of hosts to be covered with the ingress record | [] |
ingress.tls | Enable TLS configuration for the hosts defined at ingress.hosts parameter | false |
ingress.secrets | Custom TLS certificates as secrets | [] |
ingress.certManager | Enable ingress to use TLS certificates provided by Cert Manager | false |
ingress.certManagerTls | Specify TLS secret resources created by Cert Manager | [] |
ingress.className | Configure Ingress class that being used in ingress resource | "" |
Persistence
Name | Description | Value |
---|---|---|
persistence.enabled | Enable persistence using Persistent Volume Claims | true |
persistence.storageClass | Persistent Volume storage class | "" |
persistence.annotations | Additional custom annotations for the PVC | {} |
persistence.localStorage | Enable persistent volume using local storage | false |
persistence.storagePath | Local storage Path | /tmp/hostpath_pv |
persistence.localCluster | Local running cluster to provide storage space | [minikube] |
persistence.accessModes | Persistent Volume access modes | [ReadWriteOnce] |
persistence.size | Persistent Volume size | 10Gi |
storageClass.enabled | Enable Storage Class configuration | false |
storageClass.defaultClass | Create default Storage Class | false |
storageClass.bindingMode | Binding mode for Persistent Volume Claims using Storage Class | Immediate |
storageClass.allowVolumeExpansion | Allow expansion of Persistent Volume Claims using Storage Class | true |
storageClass.reclaimPolicy | Configure the retention of the dynamically created Persistent Volume | Delete |
storageClass.provisioner | Storage Class provisioner | "" |
storageClass.annotations | Additional storage class annotations | {} |
storageClass.mountOptions | Mount options used by Persistent Volumes | {} |
storageClass.parameters | Storage Class parameters | {} |
Auto update image
Name | Description | Value |
---|---|---|
autoupdate.enabled | Enable auto update Helm chart's image | true |
autoupdate.scheduler | Schedule time to run cron job to update image | "0 * * * *" |
Set parameters
When using command, specify each parameter using --set key=value[,key=value]
argument to helm install. For example, the below command deploys Appsmith and configures it to use the storage class name appsmith-pv
.
helm install \
--set persistence.storageClass=appsmith-pv \
appsmith appsmith/appsmith
Similarly, run the below command if you wish to change the encryption salt configuration.
helm install \
--set applicationConfig.APPSMITH_ENCRYPTION_SALT=123 \
appsmith appsmith/appsmith
Alternatively, use a values.yaml
file. You can specify the parameter values needed for installing the chart. To change configurations specific to Appsmith update the values.yaml
file. Listed below are available configurations for Appsmith.
Once you have made changes to the values file, run the below command.
helm install appsmith appsmith/appsmith -f values.yaml
Update Appsmith
Appsmith installation can be updated manually or by enabling auto update.
Auto update
The default Appsmith helm installation disables auto update (recommended). You have an option to enable auto update by either setting it in values file or using a command.
Values file: Ensure that the parameters are configured to enable auto update. For more information, see Auto update image. Once the set up is in place, run the below command.
helm upgrade --values values.yaml appsmith appsmith/appsmith
Command: Pass an argument using the
--set
keyword (--set autoupdate.enabled=true
) to the command.helm install appsmith/appsmith appsmith \
--set autoupdate.enabled=true
Manual update
To manually update the Appsmith container image to the latest release, run the command:
kubectl rollout restart statefulset appsmith
To upgrade from Community Edition to Business Edition, follow the instructions available at Upgrade to Business Edition for Kubernetes.
Follow the steps below to install Appsmith on your Kubernetes cluster:
Sign up on customer.appsmith.com and generate a trial license key.
Add the Appsmith
appsmith-ee
chart repository with:helm repo add appsmith-ee https://helm-ee.appsmith.com
Load the Appsmith chart repository with:
helm repo update
Generate the
values.yaml
config file:helm show values appsmith-ee/appsmith > values.yaml
To configure High Availability (HA), be sure to configure the following
Both PostgreSQL and MongoDB must be enabled or configured to point to an external instance when autoscaling
is enabled.
Install
metrics-server
, which provides vital metrics to the Horizontal Pod Autoscaler (HPA) to scale the pods.kubectl apply -f https://github.com/kubernetes-sigs/metrics-server/releases/latest/download/components.yaml
Enable
autoscaling
in thevalues.yaml
. The below shows theautoscaling
configuration for the Appsmith Deployment:autoscaling:
enabled: true
minReplicas: 2
maxReplicas: 2PostgreSQL has to be enabled Or configure an external PostgreSQL in the
applicationConfig
section invalues.yaml
.- Configure the parameters to enable PostgreSQL as shown below:
# enable PostgreSQL
postgresql:
enabled: true
auth:
username: root- Configure the parameters to point to an external PostgreSQL as shown below:
# configure an external PostgreSQL
applicationConfig::
APPSMITH_KEYCLOAK_DB_DRIVER: "postgresql"
APPSMITH_KEYCLOAK_DB_USERNAME: "<POSTGRES_USER>"
APPSMITH_KEYCLOAK_DB_PASSWORD: "<POSTGRES_PASSWORD>"
APPSMITH_KEYCLOAK_DB_URL: "<POSTGRES_DB_URL>"Enable MongoDB in the
values.yaml
or configure an external MongoDB in theapplicationConfig
invalues.yaml
.Configure the parameters to enable MongoDB as shown below:
# enable MongoDB
mongodb:
enabled: true
service:
nameOverride: appsmith-mongodbConfigure the parameters to point to an external MongoDB as shown below:
# configure an external MongoDB
applicationConfig::
APPSMITH_MONGODB_URI: "<MONGODB_URI>"
Create a shared file system. This is required for some Appsmith features that make use of the filesystem, like
git
-connected applications. Read more about this in the Create a shared file system section.
Create a shared file system
A shared file system on Kubernetes is a distributed file system that can be accessed and modified by multiple users from different pods within the Kubernetes cluster. it's used to store and share files across multiple pods, allowing users to access and collaborate on shared data.
- AWS EKS
The Amazon EFS Container Storage Interface (CSI) driver is a plugin for the Kubernetes container orchestration system that enables you to mount Amazon Elastic File System (EFS) on Kubernetes pods. Using the EFS CSI driver, you can create a shared file system on Kubernetes by mounting an EFS file system on the pods in your cluster. Follow the steps available at the official EFS CSI driver documentation to mount EFS on the Kubernetes pods.
Configure persistence
Persistence refers to the ability to store data in a way that it's retained even after the associated pod or deployment is deleted. This is important for maintaining the continuity of your applications and ensuring that important data isn't lost.
To configure persistence, you can use persistent volumes, persistent volume claims, or storage classes, depending on your platform.
- AWS EKS
- Minikube
You have the option to either configure EFS using a new Persistent Volume Claim (PVC) or using an existing PVC.
Using new PVC
This is useful when you don't have any existing PVC available or if you want to dedicate a specific PVC solely for EFS. Once the PVC is created, ensure that the following configuration is updated in values.yaml
file under persistence
attribute as shown below:
existingClaim:
enabled: false
name:
claimName:
efs:
enabled: true
driver: efs.csi.aws.com
volumeHandle: <FILE_SYSTEM_ID>
Using existing PVC
This is useful if you already have a PVC that you want to reuse for EFS or if you have multiple deployments or pods that need access to the same EFS volume. Ensure that the following configuration is updated in values.yaml
file under persistence
attribute as shown below:
existingClaim:
enabled: true
name: efsappsmith
claimName: efsappsmith
efs:
enabled: true
driver: efs.csi.aws.com
volumeHandle: <FILE_SYSTEM_ID>
localCluster:
- minikube
## @param persistence.accessModes PV Access Mode
##
accessModes:
- ReadWriteMany
## @param persistence.size PVC Storage Request
##
size: 10Gi
## Fine tuning for volumeClaimTemplates
##
existingClaim:
enabled: false
name:
claimName:
ReclaimPolicy: Retain
efs:
enabled: false
driver:
volumeHandle:
Run the below command to deploy Appsmith:
helm install appsmith appsmith-ee/appsmith -f values.yaml
When you run the install command, you may see output as shown below:
NAME: appsmith
LAST DEPLOYED: Mon Oct 24 13:24:07 2022
NAMESPACE: <namespace>
STATUS: deployed
REVISION: 1
TEST SUITE: NoneOnce deployed run the below commands to verify the installation.
To get the application URL run the below commands:
export POD_NAME=$(kubectl get pods --namespace default -l "app.kubernetes.io/name=appsmith,app.kubernetes.io/instance=appsmith-2-1670479627" -o jsonpath="{.items[0].metadata.name}")
export CONTAINER_PORT=$(kubectl get pod --namespace default $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
echo "Visit http://127.0.0.1:8080 to use your application"
kubectl --namespace default port-forward $POD_NAME 8080:$CONTAINER_PORTRun the command
kubectl get pods
to verify the list of pods. You may see output as shown below:NAME READY STATUS RESTARTS AGE
appsmith-875b6cddc-4mmj6 1/1 Running 0 90s
appsmith-875b6cddc-7b2hw 1/1 Running 0 3m30s
appsmith-875b6cddc-smzwz 1/1 Running 0 3m15s
appsmith-mongodb-0 1/1 Running 0 3m30s
appsmith-mongodb-1 1/1 Running 0 3m10s
appsmith-mongodb-arbiter-0 1/1 Running 0 3m30s
appsmith-postgresql-0 1/1 Running 0 3m30s
appsmith-redis-master-0 1/1 Running 0 3m30s
appsmith-redis-replicas-0 1/1 Running 0 3m30s
Sign-in to your instance again. Upon successful login, you see a screen where you can enter the license key and activate the instance.
Update Appsmith
Appsmith installation can be updated manually or by enabling auto update.
Auto update
The default Appsmith helm installation disables auto update (recommended). You have an option to enable auto update by either:
- Running the command below.
helm upgrade --set autoupdate.enabled=true \
appsmith [appsmith-ee|appsmith]/appsmith - Or edit
values.yaml
and specify the following parametersFollowed by running the command below.autoupdate.enabled: true
autoupdate.scheduler: 0helm upgrade --values values.yaml appsmith [appsmith-ee|appsmith]/appsmith
Manual update
To manually update the Appsmith container image to the latest release, run the command:
kubectl rollout restart deployment appsmith
Publish Appsmith
To make your Appsmith installation accessible on the internet, you need an Ingress controller set up. For more information on Ingress controllers, see the Configure Kubernetes Cluster section. If you haven't yet installed the Helm chart, you can run the following command to install the chart, enable the ingress controller, and publish Appsmith.
To install the Nginx ingress controller on AWS-EKS, GCE-GKE, or Azure, run the following command if it hasn't already been installed:
helm install ingress-nginx ingress-nginx/ingress-nginx
- Community Edition
- Business Edition
Follow the steps below to configure using command
helm upgrade appsmith/appsmith \
--set ingress.enabled=true \
--set ingress.className=nginx \
--set service.type=ClusterIP \
Follow the steps below to configure using `values.yaml`
Open the values.yaml
file and update the parameter values as below:
ingress:
## @param ingress.enabled Enable ingress record generation for Ghost
##
enabled: true
## @param ingress.annotations Additional custom annotations for the ingress record
## NOTE: If `ingress.certManager=true`, annotation `kubernetes.io/tls-acme: "true"` will automatically be added
##
className: nginx
hosts: []
# - host: appsmith-domain.me
service:
## @param service.type Kubernetes Service type
##
type: ClusterIP
Once the parameter values are modified, run the below command:
helm upgrade --values values.yaml appsmith appsmith/appsmith
Enable the ingress controller through command or by modifying the values.yaml
file.
Follow the steps below to configure using command
helm upgrade appsmith-ee/appsmith \
--set ingress.enabled=true \
--set ingress.className=nginx \
--set service.type=ClusterIP \
Follow the steps below to configure using `values.yaml`
ingress:
## @param ingress.enabled Enable ingress record generation for Ghost
##
enabled: true
## @param ingress.annotations Additional custom annotations for the ingress record
## NOTE: If `ingress.certManager=true`, annotation `kubernetes.io/tls-acme: "true"` will automatically be added
##
className: nginx
hosts: []
# - host: appsmith-domain.me
service:
## @param service.type Kubernetes Service type
##
type: ClusterIP
Once the parameter values are modified, run the below command:
helm upgrade --values values.yaml appsmith appsmith-ee/appsmith
It takes a few minutes for the ingress to get a public IP assigned. Once it has been assigned, you should see an IPv4 address or a domain name in the
ADDRESS
column. Run the below command to get this address:kubectl get ingress
The command generates the output as shown below:
NAME CLASS HOSTS ADDRESS PORTS AGE
appsmith nginx * a918d94876c27453ea78d2883539bb36-1165345706.ap-south-1.elb.amazonaws.com 80 25h
Configure TLS
To ensure the security of your Appsmith application, it's recommended to use TLS certificates. One way to do this is by using Cert Manager. Cert Manager secures HTTP traffic with TLS and SSL certificates. The Appsmith Helm chart comes with built-in support for Ingress routes and certificate management through cert-manager. This makes it easy to configure TLS support using certificates from a variety of certificate providers, including Let's Encrypt.
The steps below explain how to use Ingress routes and cert-manager to configure TLS for your Appsmith deployment using a free Let's Encrypt
certificate:
When executing these commands on Google Kubernetes Engine (GKE), you may encounter permission errors. Refer to the official cert-manager documentation for notes on how to elevate your permissions.*
Obtain the LoadBalancer host name using the command below. Note this host name as you need it to configure DNS in a later step.
kubectl get svc --namespace ingress-nginx ingress-nginx-controller -o jsonpath="{.status.loadBalancer.ingress[0].hostname}"
Browse to the host name and confirm that you can access your Appsmith instance. This indicates that the NGINX Ingress controller is working.
Configure the DNS for your domain name by adding a
CNAME
record pointing to the public host name obtained in the previous steps.To use cert-manager, add the repository, create a namespace, and create CRDs. i. Add the repository by running below command:
helm repo add jetstack https://charts.jetstack.io
ii. Create a namespace by running below command:
kubectl create namespace cert-manager
iii. Create CRDs by running below command:
kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.5.3/cert-manager.crds.yaml
To create a ClusterIssuer resource for
Let's Encrypt
certificates, create a file named letsencrypt-appsmith.yaml with the following content, replacing the <EMAIL_ADDRESS> placeholder with a valid email address:apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
name: letsencrypt-appsmith
spec:
acme:
email: <EMAIL_ADDRESS>
server: https://acme-v02.api.letsencrypt.org/directory
privateKeySecretRef:
name: letsencrypt-appsmith
solvers:
- http01:
ingress:
class: nginxApply the changes to the cluster:
kubectl apply -f letsencrypt-appsmith.yaml
Use Helm to install cert-manager and set up
Let's Encrypt
as the default Certificate Authority (CA).helm install cert-manager --namespace cert-manager jetstack/cert-manager --version v1.5.3
Install Appsmith with integration to Ingress and cert-manager.
- Community Edition
- Business Edition
Follow the below steps to configure using a command
```bash
helm upgrade appsmith appsmith/appsmith \
--set service.type=ClusterIP \
--set ingress.enabled=true \
--set ingress.tls=true \
--set ingress.certManager=true \
--set ingress.annotations."cert-manager\.io/cluster-issuer"=letsencrypt-appsmith \
--set ingress.hosts[0].host=<DOMAIN> \
--set ingress.certManagerTls[0].hosts[0]=<DOMAIN> \
--set ingress.certManagerTls[0].secretName=letsencrypt-appsmith
--set ingress.className=nginx
```
Follow the below steps to configure using a `values.yaml` file
```bash
ingress:
enabled: true
annotations:
cert-manager.io/cluster-issuer: "letsencrypt-appsmith"
hosts:
- host: example.appsmith.com
tls: true
secrets: []
certManager: true
certManagerTls:
- hosts:
- example.appsmith.com
secretName: letsencrypt-appsmith
className: "nginx"
```
Run the below command once the parameter values are updated:
```bash
helm upgrade --values values.yaml appsmith appsmith/appsmith
```
Follow the below steps to configure using a command
helm upgrade appsmith appsmith-ee/appsmith \
--set service.type=ClusterIP \
--set ingress.enabled=true \
--set ingress.tls=true \
--set ingress.certManager=true \
--set ingress.annotations."cert-manager\.io/cluster-issuer"=letsencrypt-appsmith \
--set ingress.hosts[0].host=<DOMAIN> \
--set ingress.certManagerTls[0].hosts[0]=<DOMAIN> \
--set ingress.certManagerTls[0].secretName=letsencrypt-appsmith
--set ingress.className=nginx
Follow the below steps to configure using a `values.yaml` file
ingress:
enabled: true
annotations:
cert-manager.io/cluster-issuer: "letsencrypt-appsmith"
hosts:
- host: example.appsmith.com
tls: true
secrets: []
certManager: true
certManagerTls:
- hosts:
- example.appsmith.com
secretName: letsencrypt-appsmith
className: "nginx"
Run the below command once the parameter values are updated:
helm upgrade --values values.yaml appsmith appsmith-ee/appsmith
Once the deployment is finished, check the domain in a browser to verify that the Appsmith site is accessible over a secure TLS connection with a valid Let's Encrypt
certificate.
Enable data compression for Ingress controller
The default installation doesn't have data compression configured for Nginx ingress controller. Follow the below steps to enable it.
Edit the
configMap
foringress-nginx-controller
by using the below command.kubectl edit configmap -n ingress-nginx ingress-nginx-controller
Add the following to the data section.
# Add the data section if not already present
data:
use-gzip: "true" # ENABLE GZIP COMPRESSION
gzip-types: "*" # SPECIFY MIME TYPES TO COMPRESS ("*" FOR ALL)
The Nginx controller automatically updates once you save (:wq!
) the changes.
Uninstall Appsmith
The following command uninstalls Appsmith and removes all Kubernetes resources associated with the chart:
- List the releases by running below command:
helm list
The command generates the output as shown below:
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
#highlight-next-line
appsmith-1631069261 default 1 2021-09-09 11:24:40.152766 +0700 +07 deployed appsmith-1.3.0 1.16.0
- Pick the release name
appsmith-1631069261
and run the below command to uninstall Appsmith:
helm uninstall appsmith-1631069261
- Run the command to verify the release status for
appsmith-1631069261
helm status <RELEASE_NAME>
Troubleshooting
If you’re having issues with the deployment, please see the debugging deployment errors troubleshooting guide. If you continue to have problems reach out on Discord Server or send an email to support or ask questions on the community forum.