Skip to content

Commit b0477e4

Browse files
committed
AUTO: Sync Helm Charts docs to ScalarDL docs site repo
1 parent cad0c1f commit b0477e4

6 files changed

+2
-25
lines changed

docs/helm-charts/configure-custom-values-file.mdx

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,6 @@ displayed_sidebar: docsEnglish
1010
When you deploy Scalar products using Scalar Helm Charts, you must prepare your custom values file based on your environment. Please refer to the following documents for more details on how to a create custom values file for each product.
1111

1212
* [ScalarDB Cluster](configure-custom-values-scalardb-cluster.mdx)
13-
* [ScalarDB Analytics with PostgreSQL](configure-custom-values-scalardb-analytics-postgresql.mdx)
1413
* [ScalarDL Ledger](configure-custom-values-scalardl-ledger.mdx)
1514
* [ScalarDL Auditor](configure-custom-values-scalardl-auditor.mdx)
1615
* [ScalarDL Schema Loader](configure-custom-values-scalardl-schema-loader.mdx)

docs/helm-charts/configure-custom-values-scalar-admin-for-kubernetes.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ scalarAdminForKubernetes:
103103
- effect: NoSchedule
104104
key: scalar-labs.com/dedicated-node
105105
operator: Equal
106-
value: scalardb-analytics-postgresql
106+
value: scalardb-cluster
107107
```
108108

109109
### TLS configurations (optional based on your environment)

docs/helm-charts/getting-started-scalar-helm-charts.mdx

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,6 @@ After the Kubernetes cluster starts, you can try each Scalar Helm Charts on it.
7171

7272
* [ScalarDB Cluster with TLS](getting-started-scalardb-cluster-tls.mdx)
7373
* [ScalarDB Cluster with TLS by Using cert-manager](getting-started-scalardb-cluster-tls-cert-manager.mdx)
74-
* [ScalarDB Analytics with PostgreSQL](getting-started-scalardb-analytics-postgresql.mdx)
7574
* [ScalarDL Ledger and Auditor with TLS (Auditor mode)](getting-started-scalardl-auditor-tls.mdx)
7675
* [ScalarDL Ledger and Auditor with TLS by Using cert-manager (Auditor mode)](getting-started-scalardl-auditor-tls-cert-manager.mdx)
7776
* [ScalarDL Ledger (Ledger only)](getting-started-scalardl-ledger.mdx)

docs/helm-charts/how-to-deploy-scalar-products.mdx

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -56,14 +56,12 @@ If you're using any of the following products from the public container reposito
5656
* Scalar Envoy (deploy with ScalarDB Cluster, ScalarDL Ledger, or ScalarDL Auditor)
5757
* ScalarDL Schema Loader
5858
* Scalar Admin for Kubernetes
59-
* ScalarDB Analytics with PostgreSQL
6059

6160
## Deploy Scalar products
6261

6362
Please refer to the following documents for more details on how to deploy each product.
6463

6564
* [ScalarDB Cluster](how-to-deploy-scalardb-cluster.mdx)
66-
* [ScalarDB Analytics with PostgreSQL](how-to-deploy-scalardb-analytics-postgresql.mdx)
6765
* [ScalarDL Ledger](how-to-deploy-scalardl-ledger.mdx)
6866
* [ScalarDL Auditor](how-to-deploy-scalardl-auditor.mdx)
6967
* [Scalar Admin for Kubernetes](how-to-deploy-scalar-admin-for-kubernetes.mdx)

docs/helm-charts/mount-files-or-volumes-on-scalar-pods.mdx

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ displayed_sidebar: docsEnglish
77

88
# Mount any files or volumes on Scalar product pods
99

10-
You can mount any files or volumes on Scalar product pods when you use ScalarDB Server, ScalarDB Cluster, ScalarDB Analytics with PostgreSQL, or ScalarDL Helm Charts (ScalarDL Ledger and ScalarDL Auditor).
10+
You can mount any files or volumes on Scalar product pods when you use ScalarDB Server, ScalarDB Cluster, or ScalarDL Helm Charts (ScalarDL Ledger and ScalarDL Auditor).
1111

1212
## Mount key and certificate files on a pod in ScalarDL Helm Charts
1313

@@ -115,7 +115,6 @@ You can mount emptyDir to Scalar product pods by using the following keys in you
115115
* Keys
116116
* `scalardb.extraVolumes` / `scalardb.extraVolumeMounts` (ScalarDB Server)
117117
* `scalardbCluster.extraVolumes` / `scalardbCluster.extraVolumeMounts` (ScalarDB Cluster)
118-
* `scalardbAnalyticsPostgreSQL.extraVolumes` / `scalardbAnalyticsPostgreSQL.extraVolumeMounts` (ScalarDB Analytics with PostgreSQL)
119118
* `ledger.extraVolumes` / `ledger.extraVolumeMounts` (ScalarDL Ledger)
120119
* `auditor.extraVolumes` / `auditor.extraVolumeMounts` (ScalarDL Auditor)
121120

docs/helm-charts/use-secret-for-credentials.mdx

Lines changed: 0 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -51,16 +51,6 @@ SCALAR_DB_CLUSTER_MEMBERSHIP_KUBERNETES_ENDPOINT_NAME
5151
...
5252
```
5353
</TabItem>
54-
<TabItem value="scalardb-analytics-with-postgresql" label="ScalarDB Analytics with PostgreSQL">
55-
```yaml
56-
scalardbAnalyticsPostgreSQL:
57-
databaseProperties: |
58-
...
59-
scalar.db.username=${env:SCALAR_DB_USERNAME}
60-
scalar.db.password=${env:SCALAR_DB_PASSWORD}
61-
...
62-
```
63-
</TabItem>
6454
<TabItem value="scalardb-server" label="ScalarDB Server (Deprecated)">
6555
<h3>ScalarDB Server 3.8 or later (Apache Commons Text syntax)</h3>
6656
@@ -176,14 +166,6 @@ SCALAR_DB_CLUSTER_MEMBERSHIP_KUBERNETES_ENDPOINT_NAME
176166
secretName: "scalardb-cluster-credentials-secret"
177167
```
178168
</TabItem>
179-
<TabItem value="scalardb-analytics-with-postgresql" label="ScalarDB Analytics with PostgreSQL">
180-
**Key:** `scalardbAnalyticsPostgreSQL.secretName`
181-
182-
```yaml
183-
scalardbAnalyticsPostgreSQL:
184-
secretName: "scalardb-analytics-postgresql-credentials-secret"
185-
```
186-
</TabItem>
187169
<TabItem value="scalardb-server" label="ScalarDB Server (Deprecated)">
188170
**Key:** `scalardb.secretName`
189171

0 commit comments

Comments
 (0)