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: docs/self-hosting/govern/plane-ai.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ For an overview of what Plane AI can do, see the [Plane AI](https://docs.plane.s
14
14
15
15
You'll need:
16
16
17
-
- An OpenSearch 2.x instance (self-hosted or AWS OpenSearch) configured for [advanced search](/self-hosting/govern/advanced-search).
17
+
- An OpenSearch instance running version 2.19 or later (self-hosted or AWS OpenSearch) configured for [advanced search](/self-hosting/govern/advanced-search).
18
18
- At least one LLM provider API key or a custom OpenAI-compatible endpoint.
19
19
- At least one embedding model configured in OpenSearch.
Copy file name to clipboardExpand all lines: docs/self-hosting/methods/kubernetes.md
+45-10Lines changed: 45 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,15 +31,15 @@ Ensure you use use the latest Helm chart version.
31
31
2. Set the following environment variables:
32
32
33
33
```bash
34
-
PLANE_VERSION=v2.3.1
34
+
PLANE_VERSION=v2.4.0
35
35
```
36
36
37
37
```bash
38
38
DOMAIN_NAME=<subdomain.domain.tld or domain.tld>
39
39
```
40
40
41
41
::: warning
42
-
When configuring the PLANE_VERSION environment variable, **do not** set it to `stable`. Always specify the latest version number (e.g., `2.3.1`). Using `stable` can lead to unexpected issues.
42
+
When configuring the PLANE_VERSION environment variable, **do not** set it to `stable`. Always specify the latest version number (e.g., `2.4.0`). Using `stable` can lead to unexpected issues.
| planeVersion | v2.3.1 | Yes | Specifies the version of Plane to be deployed. Copy this from prime.plane.so. |
116
+
| planeVersion | v2.4.0 | Yes | Specifies the version of Plane to be deployed. Copy this from prime.plane.so. |
117
117
| 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. |
| airgapped.enabled | false | No | Specifies the airgapped mode the Plane API runs in. |
124
-
| airgapped.s3SecretName | "" | No | Name of the Secret that contains the CA certificate (.crt). The Secret must include a data key whose filename matches the basename of `airgapped.s3SecretKey` (default: `s3-custom-ca.crt`). Used to override S3’s CA when `airgapped.enabled=true`. Applying this secret looks like: `kubectl -n plane create secret generic plane-s3-ca \ --from-file=s3-custom-ca.crt=/path/to/your/ca.crt` |
125
-
| airgapped.s3SecretKey | "" | No | Key name of the secret to load the Custom Root CA from `airgapped.s3SecretName` |
| airgapped.enabled | false | No | Enable airgapped mode for the Plane API. |
124
+
| airgapped.s3Secrets | [] | No | List of Kubernetes Secrets containing CA certificates to install. Each entry requires `name` (Secret name) and `key` (filename in the Secret). Example: `kubectl -n plane create secret generic plane-s3-ca --from-file=s3-custom-ca.crt=/path/to/ca.crt`. Supports multiple certs (e.g. S3 + internal CA). Available in v2.4.0 and later. |
125
+
| airgapped.s3SecretName | "" | No | **Deprecated** <br/> Name of a single Kubernetes Secret containing the S3 CA cert. Used only when `s3Secrets` is empty. Use `s3Secrets` instead. |
126
+
| airgapped.s3SecretKey | "" | No | **Deprecated** <br/> Key (filename) of the cert file inside the Secret. Used only when `s3Secrets` is empty. Set together with `airgapped.s3SecretName`. Use `s3Secrets` instead. |
127
+
128
+
#### CA certificate configuration (For airgapped deployments only)
129
+
130
+
Plane supports custom CA certificates for connecting to S3-compatible storage and other internal services in airgapped environments.
131
+
132
+
- **New deployments:** Use `airgapped.s3Secrets` as shown in the table above.
133
+
- **Existing deployments using `s3SecretName` and `s3SecretKey`:** Your configuration still works. Migrate only if you need to use multiple CA certificates.
134
+
135
+
#### Migrating to the new configuration
136
+
137
+
:::warning
138
+
Requires Plane v2.4.0 or later.
139
+
:::
140
+
141
+
The new `s3Secrets` configuration supports multiple CA certificates, useful if you need to trust certificates from different sources (e.g., S3 endpoint CA and internal PKI). If you only need a single certificate, migration is optional.
142
+
143
+
To migrate:
144
+
145
+
1. Add your existing secret to the `s3Secrets` list:
146
+
147
+
```yaml
148
+
airgapped:
149
+
enabled: true
150
+
s3Secrets:
151
+
- name: plane-s3-ca # your existing s3SecretName value
152
+
key: s3-custom-ca.crt # your existing s3SecretKey value
153
+
154
+
155
+
# s3SecretName and s3SecretKey can be removed after migration
156
+
```
157
+
158
+
2. Remove `s3SecretName` and `s3SecretKey` from your values file.
0 commit comments