You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: self-hosting/methods/kubernetes.mdx
+37-24Lines changed: 37 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,29 +31,28 @@ Plane One and Plane Pro are enabled on this edition, so the Free plan on this ed
31
31
32
32
4. Use one of the following ways to deploy Plane:
33
33
-**Quick setup**:
34
-
This is the fastest way to deploy Plane with the default settings. This will create stateful deployments for Postgres, Redis, and Minio with a persistent volume claim using the `longhorn` storage class. This also sets up the Ingress routes for you using `nginx` ingress class. To customize these settings, see the **Custom ingress routes** section on this page.
34
+
This is the fastest way to deploy Plane with the default settings. This will create stateful deployments for Postgres, Redis/Valkey, and Minio with a persistent volume claim using the `longhorn` storage class. This also sets up the Ingress routes for you using `nginx` ingress class. To customize these settings, see the [Custom ingress routes](#custom-ingress-routes).
This is the minimum required to set up Plane Commercial edition. You can change the default namespace from `plane`, the default app name from `plane-app`, the default storage class from `longhorn`, and the default ingress class from `nginx` to
55
-
whatever you would like to.<br/> <br/>
56
-
You can also pass other settings referring to `Configuration Settings` section.
54
+
This is the minimum required to set up Plane Commercial edition. You can change the default namespace from `plane`, the default app name from `plane-app`, the default storage class from `longhorn`, and the default ingress class from `nginx` to whatever you would like to.<br/> <br/>
55
+
You can also pass other settings referring to the **Configuration Settings** toggle section below.
57
56
</Note>
58
57
59
58
-**Advanced setup**:
@@ -75,18 +74,18 @@ Plane One and Plane Pro are enabled on this edition, so the Free plan on this ed
75
74
-`ingress.ingressClass: <nginx or any other ingress class configured in your cluster>`
76
75
-`env.storageClass: <longhorn or any other storage class configured in your cluster>`
77
76
78
-
See the **Configuration settings** section for more details.
77
+
See the **Configuration settings**toggle section for more details.
79
78
80
79
2. After saving the `values.yaml` file, run the following command to deploy Plane:
81
80
82
81
```bash
83
82
helm install plane-app plane/plane-enterprise \
84
-
--create-namespace \
85
-
--namespace plane \
86
-
-f values.yaml \
87
-
--timeout 10m \
88
-
--wait \
89
-
--wait-for-jobs
83
+
--create-namespace \
84
+
--namespace plane \
85
+
-f values.yaml \
86
+
--timeout 10m \
87
+
--wait \
88
+
--wait-for-jobs
90
89
```
91
90
5. If you want to upgrade to a paid plan, see [Plane upgrades](/workspaces-and-users/upgrade-plan).
92
91
@@ -106,7 +105,7 @@ Plane One and Plane Pro are enabled on this edition, so the Free plan on this ed
106
105
107
106
| Setting | Default | Required | Description |
108
107
|---|:---:|:---:|---|
109
-
| planeVersion | v1.2.1| Yes | Specifies the version of Plane to be deployed. Copy this from prime.plane.so. |
108
+
| planeVersion | v1.3.0 | Yes | Specifies the version of Plane to be deployed. Copy this from `prime.plane.so.`|
110
109
| license.licenseServer |`https://prime.plane.so`| Yes | Sets the value of the `licenseServer` that gets you your license and validates it periodically. Don't change this. |
111
110
| license.licenseDomain | 'plane.example.com' | Yes | The fully-qualified domain name (FQDN) in the format `sudomain.domain.tld` or `domain.tld` that the license is bound to. It is also attached to your `ingress` host to access Plane. |
112
111
@@ -125,7 +124,7 @@ Plane One and Plane Pro are enabled on this edition, so the Free plan on this ed
125
124
| services.postgres.assign_cluster_ip | false || Set it to `true` if you want to assign `ClusterIP` to the service |
126
125
| env.pgdb_remote_url ||| Users can also decide to use the remote hosted database and link to Plane deployment. Ignoring all the above keys, set `services.postgres.local_setup` to `false` and set this key with remote connection url. |
127
126
128
-
#### Redis Setup
127
+
#### Redis/Valkey Setup
129
128
130
129
| Setting | Default | Required | Description |
131
130
|---|:---:|:---:|---|
@@ -183,6 +182,19 @@ Plane One and Plane Pro are enabled on this edition, so the Free plan on this ed
183
182
| services.admin.image|`registry.plane.tools/plane/admin-enterprise`|| This deployment needs a preconfigured docker image to function. Docker image name is provided by the owner and must not be changed for this deployment |
184
183
| services.admin.assign_cluster_ip | false || Set it to `true` if you want to assign `ClusterIP` to the service |
185
184
185
+
#### Live Service Deployment
186
+
187
+
| Setting | Default | Required | Description |
188
+
|---|:---:|:---:|---|
189
+
| services.live.replicas | 1 | Yes | Kubernetes helps you with scaling up/down the deployments. You can run 1 or more pods for each deployment. This key helps you setting up number of replicas you want to run for this deployment. It must be >=1 |
190
+
| services.live.memoryLimit | 1000Mi || Every deployment in kubernetes can be set to use maximum memory they are allowed to use. This key sets the memory limit for this deployment to use.|
191
+
| services.live.cpuLimit | 500m || Every deployment in kubernetes can be set to use maximum cpu they are allowed to use. This key sets the cpu limit for this deployment to use.|
192
+
| services.live.image| registry.plane.tools/plane/live-enterprise || This deployment needs a preconfigured docker image to function. Docker image name is provided by the owner and must not be changed for this deployment |
193
+
| env.live_sentry_dsn ||| (optional) Live service deployment comes with some of the preconfigured integration. Sentry is one among those. Here user can set the Sentry provided DSN for this integration.|
194
+
| env.live_sentry_environment ||| (optional) Live service deployment comes with some of the preconfigured integration. Sentry is one among those. Here user can set the Sentry environment name (as configured in Sentry) for this integration.|
195
+
| env.live_sentry_traces_sample_rate ||| (optional) Live service deployment comes with some of the preconfigured integration. Sentry is one among those. Here user can set the Sentry trace sample rate (as configured in Sentry) for this integration.|
196
+
| services.live.assign_cluster_ip | false || Set it to `true` if you want to assign `ClusterIP` to the service |
197
+
186
198
#### Monitor Deployment
187
199
188
200
| Setting | Default | Required | Description |
@@ -461,6 +473,7 @@ To install our Community Edition, please follow these steps below.
0 commit comments