> ## Documentation Index
> Fetch the complete documentation index at: https://enterprise-docs.dify.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Testing Deployment

## Requirements

This is the recommended configuration for testing deployment or staging deployment. You can adjust the configuration based on your requirements.

* Kubernetes Cluster
  * 1 Worker Nodes: 4 CPU, 16 GB RAM
* Container Registry (Plugins)
  * AWS ECR（with AK/SK or IRSA）/ Azure ACR / Aliyun ACR (with AK/SK) / Tencent TCR (with AK/SK) / Dockerhub / Google Artifact Registry
* Persistence Storage
  * S3 / AWS S3 (with AK/SK or IRSA) / Azure Blob / Aliyun OSS (with AK/SK) / Tencent COS (with AK/SK) / Google GCS
  * 100 GB Storage
* Postgres Database
  * Version 14+
  * 4 CPU, 8 GB RAM
  * At least 512G SSD
* Redis Database
  * Version 6+
  * 1 GB RAM
* [Vector DB Virtual Machine - Qdrant Single Node](/versions/3-0-x/en-us/deployment/advanced-configuration/qdrant/single-node)
  * 1 Virtual Machines
  * 4 CPU, 8 GB RAM
  * 100 GB Storage

## Deployment

### 1. Get Helm Repository Info

```bash theme={null}
helm repo add dify https://langgenius.github.io/dify-helm
helm repo update
```

For more information, please refer to the [Dify Helm Chart](/versions/3-0-x/en-us/deployment/advanced-configuration/dify-helm-chart).

### 2. Save Helm Chart Values

* Save Helm chart values to a file named `values.yaml`.
* Update the `values.yaml` file with your configuration.

<Warning>
  - Please replace the `#REPLACE_ME#` placeholders with your actual values.
  - Please replace "dify123456" with your own value.
  - The `global.appSecretKey` and `enterprise.appSecretKey` must be different.
</Warning>

```yaml theme={null}
###################################
# Please replace "dify123456" with your own value
###################################
global:
  appSecretKey: 'dify123456'
  innerApiKey: 'dify123456'
  consoleApiDomain: "console.dify.local"
  consoleWebDomain: "console.dify.local"
  serviceApiDomain: "api.dify.local"
  appApiDomain: "app.dify.local"
  appWebDomain: "app.dify.local"
  filesDomain: "upload.dify.local"
  enterpriseDomain: "enterprise.dify.local"

ingress:
  enabled: true
  className: "nginx"
  annotations: {
    # set file upload size limit
    nginx.ingress.kubernetes.io/proxy-body-size: "15m"
  }

api:
  replicas: 3
  serverWorkerAmount: 1
worker:
  replicas: 3
  celeryWorkerAmount: 1
web:
  replicas: 1
sandbox:
  replicas: 1
enterpriseAudit:
  replicas: 1
enterprise:
  replicas: 1
  appSecretKey: "dify123456"
  adminAPIsSecretKeySalt: "dify123456"
enterpriseFrontend:
  replicas: 1
ssrfProxy:
  replicas: 1
unstructured:
  replicas: 1
plugin_daemon:
  replicas: 1
plugin_controller:
  replicas: 1
plugin_connector:
  replicas: 1
plugin_manager:
  replicas: 1
gateway:
  replicas: 1

###################################
# Persistence Configration
###################################
persistence:
  type: "s3"
  s3:
    endpoint: "https://xxx.r2.cloudflarestorage.com"
    accessKey: "#REPLACE_ME#"
    secretKey: "#REPLACE_ME#"
    region: "us-east-1"
    bucketName: "your-bucket-name"
    addressType: ""
    useAwsManagedIam: false
    useAwsS3: true

###################################
# External postgres
###################################
externalPostgres:
  enabled: true
  address: "#REPLACE_ME#"
  port: 5432
  credentials:
    dify:
      database: "dify"
      username: "postgres"
      password: "#REPLACE_ME#"
      sslmode: "require"
    plugin_daemon:
      database: "dify_plugin_daemon"
      username: "postgres"
      password: "#REPLACE_ME#"
      sslmode: "require"
    enterprise:
      database: "enterprise"
      username: "postgres"
      password: "#REPLACE_ME#"
      sslmode: "require"
    audit:
      database: "audit"
      username: "postgres"
      password: "#REPLACE_ME#"
      sslmode: "require"

###################################
# External Redis
###################################
externalRedis:
  enabled: true
  host: "#REPLACE_ME#"
  port: 6379
  username: ""
  password: "#REPLACE_ME#"
  useSSL: false

###################################
# External Qdrant
###################################
vectorDB:
  useExternal: true
  externalType: "qdrant"
  externalQdrant:
    endpoint: "http://your-qdrant-cluster-url.qdrant.tech/"
    apiKey: "#REPLACE_ME#"

imagePullSecrets: []
```

### 3. Configure `Container Registry`

* 3.1 Container Registry for Plugins
  * For more information, please refer to the [Container Registry for Plugins](/versions/3-0-x/en-us/deployment/advanced-configuration/container-registry-for-plugins).
* 3.2 Container Registry for Services
  * For more information, please refer to the [Container Registry](/versions/3-0-x/en-us/deployment/advanced-configuration/container-registry).

### 4. Configure `Persistence Storage`

* For more information, please refer to the [Persistence Storage](/versions/3-0-x/en-us/deployment/advanced-configuration/persistent-storage).

### 5. Configure `External postgres`

* For more information, please refer to the [External Postgres](/versions/3-0-x/en-us/deployment/advanced-configuration/postgresql-database).

### 6. Configure `External Redis`

* For more information, please refer to the [External Redis](/versions/3-0-x/en-us/deployment/advanced-configuration/redis).

### 7. Configure `External Qdrant`

* For more information, please refer to the [External Single Node Qdrant](/versions/3-0-x/en-us/deployment/advanced-configuration/qdrant/single-node).

### 8. Configure `Ingress Controller`

* For more information, please refer to the [Ingress Controller](/versions/3-0-x/en-us/deployment/advanced-configuration/nginx-ingress-controller).

### 9. Install Dify Helm Chart

```bash theme={null}
helm upgrade -i dify -f values.yaml dify/dify
```

### 10. Verify Installation

* For more information, please refer to the [Verify Services Status](/versions/3-0-x/en-us/deployment/verify-services-status).

## Advanced Configuration

### 1. Domain and SSL Certificate

* For more information, please refer to the [Domain and SSL Certificate](/versions/3-0-x/en-us/deployment/advanced-configuration/domain-and-ssl-certificate).

### 2. Email Provider

* For more information, please refer to the [Email Provider](/versions/3-0-x/en-us/deployment/advanced-configuration/email-provider).

### 3. Performance Tuning

* For more information, please refer to the [Performance Tuning](/versions/3-0-x/en-us/deployment/advanced-configuration/performance).
