From cd6dad65a766087db80543aa8b02fec05ffa8849 Mon Sep 17 00:00:00 2001 From: josh-wong Date: Mon, 17 Nov 2025 04:26:49 +0000 Subject: [PATCH] AUTO: Sync Helm Charts docs to ScalarDL docs site repo --- .../configure-custom-values-file.mdx | 1 - ...stom-values-scalar-admin-for-kubernetes.mdx | 2 +- .../getting-started-scalar-helm-charts.mdx | 1 - .../how-to-deploy-scalar-products.mdx | 2 -- .../mount-files-or-volumes-on-scalar-pods.mdx | 3 +-- .../helm-charts/use-secret-for-credentials.mdx | 18 ------------------ 6 files changed, 2 insertions(+), 25 deletions(-) diff --git a/versioned_docs/version-3.9/helm-charts/configure-custom-values-file.mdx b/versioned_docs/version-3.9/helm-charts/configure-custom-values-file.mdx index 9e59653a..e11a49c5 100644 --- a/versioned_docs/version-3.9/helm-charts/configure-custom-values-file.mdx +++ b/versioned_docs/version-3.9/helm-charts/configure-custom-values-file.mdx @@ -10,7 +10,6 @@ displayed_sidebar: docsEnglish 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. * [ScalarDB Cluster](configure-custom-values-scalardb-cluster.mdx) -* [ScalarDB Analytics with PostgreSQL](configure-custom-values-scalardb-analytics-postgresql.mdx) * [ScalarDL Ledger](configure-custom-values-scalardl-ledger.mdx) * [ScalarDL Auditor](configure-custom-values-scalardl-auditor.mdx) * [ScalarDL Schema Loader](configure-custom-values-scalardl-schema-loader.mdx) diff --git a/versioned_docs/version-3.9/helm-charts/configure-custom-values-scalar-admin-for-kubernetes.mdx b/versioned_docs/version-3.9/helm-charts/configure-custom-values-scalar-admin-for-kubernetes.mdx index 43b8f5e3..88cfbb0d 100644 --- a/versioned_docs/version-3.9/helm-charts/configure-custom-values-scalar-admin-for-kubernetes.mdx +++ b/versioned_docs/version-3.9/helm-charts/configure-custom-values-scalar-admin-for-kubernetes.mdx @@ -103,7 +103,7 @@ scalarAdminForKubernetes: - effect: NoSchedule key: scalar-labs.com/dedicated-node operator: Equal - value: scalardb-analytics-postgresql + value: scalardb-cluster ``` ### TLS configurations (optional based on your environment) diff --git a/versioned_docs/version-3.9/helm-charts/getting-started-scalar-helm-charts.mdx b/versioned_docs/version-3.9/helm-charts/getting-started-scalar-helm-charts.mdx index d51d95db..b149ca1f 100644 --- a/versioned_docs/version-3.9/helm-charts/getting-started-scalar-helm-charts.mdx +++ b/versioned_docs/version-3.9/helm-charts/getting-started-scalar-helm-charts.mdx @@ -71,7 +71,6 @@ After the Kubernetes cluster starts, you can try each Scalar Helm Charts on it. * [ScalarDB Cluster with TLS](getting-started-scalardb-cluster-tls.mdx) * [ScalarDB Cluster with TLS by Using cert-manager](getting-started-scalardb-cluster-tls-cert-manager.mdx) -* [ScalarDB Analytics with PostgreSQL](getting-started-scalardb-analytics-postgresql.mdx) * [ScalarDL Ledger and Auditor with TLS (Auditor mode)](getting-started-scalardl-auditor-tls.mdx) * [ScalarDL Ledger and Auditor with TLS by Using cert-manager (Auditor mode)](getting-started-scalardl-auditor-tls-cert-manager.mdx) * [ScalarDL Ledger (Ledger only)](getting-started-scalardl-ledger.mdx) diff --git a/versioned_docs/version-3.9/helm-charts/how-to-deploy-scalar-products.mdx b/versioned_docs/version-3.9/helm-charts/how-to-deploy-scalar-products.mdx index a9489c1b..52d6cf01 100644 --- a/versioned_docs/version-3.9/helm-charts/how-to-deploy-scalar-products.mdx +++ b/versioned_docs/version-3.9/helm-charts/how-to-deploy-scalar-products.mdx @@ -56,14 +56,12 @@ If you're using any of the following products from the public container reposito * Scalar Envoy (deploy with ScalarDB Cluster, ScalarDL Ledger, or ScalarDL Auditor) * ScalarDL Schema Loader * Scalar Admin for Kubernetes -* ScalarDB Analytics with PostgreSQL ## Deploy Scalar products Please refer to the following documents for more details on how to deploy each product. * [ScalarDB Cluster](how-to-deploy-scalardb-cluster.mdx) -* [ScalarDB Analytics with PostgreSQL](how-to-deploy-scalardb-analytics-postgresql.mdx) * [ScalarDL Ledger](how-to-deploy-scalardl-ledger.mdx) * [ScalarDL Auditor](how-to-deploy-scalardl-auditor.mdx) * [Scalar Admin for Kubernetes](how-to-deploy-scalar-admin-for-kubernetes.mdx) diff --git a/versioned_docs/version-3.9/helm-charts/mount-files-or-volumes-on-scalar-pods.mdx b/versioned_docs/version-3.9/helm-charts/mount-files-or-volumes-on-scalar-pods.mdx index a8adcce6..2260cd6e 100644 --- a/versioned_docs/version-3.9/helm-charts/mount-files-or-volumes-on-scalar-pods.mdx +++ b/versioned_docs/version-3.9/helm-charts/mount-files-or-volumes-on-scalar-pods.mdx @@ -7,7 +7,7 @@ displayed_sidebar: docsEnglish # Mount any files or volumes on Scalar product pods -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). +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). ## Mount key and certificate files on a pod in ScalarDL Helm Charts @@ -115,7 +115,6 @@ You can mount emptyDir to Scalar product pods by using the following keys in you * Keys * `scalardb.extraVolumes` / `scalardb.extraVolumeMounts` (ScalarDB Server) * `scalardbCluster.extraVolumes` / `scalardbCluster.extraVolumeMounts` (ScalarDB Cluster) - * `scalardbAnalyticsPostgreSQL.extraVolumes` / `scalardbAnalyticsPostgreSQL.extraVolumeMounts` (ScalarDB Analytics with PostgreSQL) * `ledger.extraVolumes` / `ledger.extraVolumeMounts` (ScalarDL Ledger) * `auditor.extraVolumes` / `auditor.extraVolumeMounts` (ScalarDL Auditor) diff --git a/versioned_docs/version-3.9/helm-charts/use-secret-for-credentials.mdx b/versioned_docs/version-3.9/helm-charts/use-secret-for-credentials.mdx index 12499460..ffd5e1eb 100644 --- a/versioned_docs/version-3.9/helm-charts/use-secret-for-credentials.mdx +++ b/versioned_docs/version-3.9/helm-charts/use-secret-for-credentials.mdx @@ -51,16 +51,6 @@ SCALAR_DB_CLUSTER_MEMBERSHIP_KUBERNETES_ENDPOINT_NAME ... ``` - - ```yaml - scalardbAnalyticsPostgreSQL: - databaseProperties: | - ... - scalar.db.username=${env:SCALAR_DB_USERNAME} - scalar.db.password=${env:SCALAR_DB_PASSWORD} - ... - ``` -

ScalarDB Server 3.8 or later (Apache Commons Text syntax)

@@ -176,14 +166,6 @@ SCALAR_DB_CLUSTER_MEMBERSHIP_KUBERNETES_ENDPOINT_NAME secretName: "scalardb-cluster-credentials-secret" ``` - - **Key:** `scalardbAnalyticsPostgreSQL.secretName` - - ```yaml - scalardbAnalyticsPostgreSQL: - secretName: "scalardb-analytics-postgresql-credentials-secret" - ``` - **Key:** `scalardb.secretName`