Add new chart for ScalarDB Analytics with PostgreSQL #242

kota2and3kan · 2023-11-07T08:44:56Z

Description

This PR adds a new helm chart for ScalarDB Analytics with PostgreSQL!

Deploying ScalarDB Analytics with PostgreSQL on the Kubernetes environment manually takes a bit of time and effort. Instead of that, this chart can help users to deploy ScalarDB Analytics with PostgreSQL on the Kubernetes environment.

Related issues and/or PRs

N/A

Changes made

Add a new chart (new resource manifests).
Add new test for this new chart in the CI.
Add new documents that describes how to use this new chart.
Update existing documents to add the descriptions of this new chart.

Checklist

I have commented my code, particularly in hard-to-understand areas.
I have updated the documentation to reflect the changes.
Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
Tests (unit, integration, etc.) have been added for the changes.
My changes generate no new warnings.
Any dependent changes in other PRs have been merged and published.

Additional notes (optional)

Regarding getting started guide

I will create Getting started guide in another PR after related issue scalar-labs/scalardb-analytics-postgresql#44 fixed on ScalarDB Analytics with PostgreSQL side.

Overview of what you need to run `ScalarDB Analytics with PostgreSQL`

In arbitrary platforms including other environments than Kubernetes, when you run ScalarDB Analytics with PostgreSQL, you need to run the following two steps.

Before running ScalarDB Analytics with PostgreSQL (there are several backend databases).
```
+-------------------+
| Backend databases |
+-------------------+
```

Run ScalarDB Analytics with PostgreSQL container as a first step.

+-------------------+      +------------------------------------+
| Backend databases | <--- | ScalarDB Analytics with PostgreSQL |
+-------------------+      +------------------------------------+

Run Schema Importer against the ScalarDB Analytics with PostgreSQL container to load some objects into PostgreSQL as a second step.

+-------------------+      +------------------------------------+                       +-----------------+
| Backend databases | <--- | ScalarDB Analytics with PostgreSQL | <---(load objects)--- | Schema Importer |
+-------------------+      +------------------------------------+                       +-----------------+

These are the general way to run ScalarDB Analytics with PostgreSQL.

How this chart deploy `ScalarDB Analytics with PostgreSQL`

In this chart, it combines ScalarDB Analytics with PostgreSQL and Schema Importer into one Pod. And, run Schema Importer automatically in the pod.

Before running ScalarDB Analytics with PostgreSQL pod (there are several backend databases).
```
+-------------------+
| Backend databases |
+-------------------+
```

Run ScalarDB Analytics with PostgreSQL pod.

                           +--[Pod]-----------------------------------------+
                           |                                                |
                           |  +------------------------------------+        |
                           |  | ScalarDB Analytics with PostgreSQL |        |
+-------------------+      |  +------------------------------------+        |
| Backend databases | <--- |                                                |
+-------------------+      |  +-----------------+                           |
                           |  | Schema Importer |                           |
                           |  +-----------------+                           |
                           |                                                |
                           +------------------------------------------------+

Automatically, run Schema Importer against the ScalarDB Analytics with PostgreSQL container in the pod.

                           +--[Pod]-----------------------------------------+
                           |                                                |
                           |  +------------------------------------+        |
                           |  | ScalarDB Analytics with PostgreSQL | <---+  |
+-------------------+      |  +------------------------------------+     |  |
| Backend databases | <--- |                                             |  |
+-------------------+      |  +-----------------+                        |  |
                           |  | Schema Importer | ---(load objects)------+  |
                           |  +-----------------+                           |
                           |                                                |
                           +------------------------------------------------+

If Schema Importer fails because PostgreSQL is not started yet, entrypoint.sh retries to run the Schema Importer several times (10 times by default).

                           +--[Pod]-----------------------------------------+
                           |                                                |
                           |  +------------------------------------+        |
                           |  | ScalarDB Analytics with PostgreSQL | <---+  |
+-------------------+      |  +------------------------------------+     |  |
| Backend databases | <--- |                                             |  |
+-------------------+      |  +-----------------+                        |  |
                           |  | Schema Importer | ---(retry if failed)---+  |
                           |  +-----------------+                           |
                           |                                                |
                           +------------------------------------------------+

After Schema Importer succeeds, the Schema Importer container will sleep endlessly (run the sleep inf command).

                           +--[Pod]-----------------------------------------+
                           |                                                |
                           |  +------------------------------------+        |
                           |  | ScalarDB Analytics with PostgreSQL |        |
+-------------------+      |  +------------------------------------+        |
| Backend databases | <--- |                                                |
+-------------------+      |  +-----------------------------+               |
                           |  | Schema Importer (sleep inf) |               |
                           |  +-----------------------------+               |
                           |                                                |
                           +------------------------------------------------+

Release notes

Add a new chart for ScalarDB Analytics with PostgreSQL. By using this new chart, you can deploy ScalarDB Analytics with PostgreSQL on the Kubernetes environment.

kota2and3kan · 2023-11-15T07:16:59Z

charts/scalardb-analytics-postgresql/Chart.yaml

+version: 1.0.0-SNAPSHOT
+appVersion: 3.10.2


At this time, ScalarDB Analytics with PostgreSQL does not release the SNAPSHOT version. So, I set the latest stable version.

However, we are working on releasing the SNAPSHOT version on the ScalarDB Analytics with PostgreSQL side. In the future, we will set the SNAPSHOT version here.

kota2and3kan · 2023-11-15T07:21:20Z

charts/scalardb-analytics-postgresql/README.md

@@ -0,0 +1,54 @@
+# scalardb-analytics-postgresql


This file is automatically generated based on the values.yaml file.

Just curious. How is this file generated?

You can generate this file by using helm-docs.
https://github.com/norwoodj/helm-docs

Also, in our repository, you can run the helm-docs by using the following script.
https://github.com/scalar-labs/helm-charts/blob/main/scripts/update-chart-docs.sh

kota2and3kan · 2023-11-15T07:22:00Z

charts/scalardb-analytics-postgresql/ci/scalardb-analytics-postgresql-ct-values.yaml

+scalardbAnalyticsPostgreSQL:
+  databaseProperties: |
+    scalar.db.storage=jdbc
+    scalar.db.contact_points=jdbc:postgresql://postgresql.default.svc.cluster.local:5432/postgres
+    scalar.db.username=postgres
+    scalar.db.password=postgres
+
+schemaImporter:
+  namespaces:
+    - ct


This file is a custom values file for the testing in the CI.

kota2and3kan · 2023-11-15T07:29:13Z

charts/scalardb-analytics-postgresql/templates/scalardb-analytics-postgresql/configmap.yaml

+  entrypoint.sh: |
+    #!/bin/bash


At this time, I create the entorypoint.sh on the helm chart side. Schema Importer container mounts this file and runs it as an entrypoint.

The main purpose of this shell is to implement the retry process for Schema Importer.

We need this file on the helm chart side to run the existing stable versions (v3.10) images.

However, I will create this entrypoint.sh on the Schema Imorter container image side in the future. After that (maybe after v3.11), we can use the etntrypoint.sh that is included in the container image.

So, this runs Schema Importer every time the pod starts?

Yes. That's right. For example, we run Schema Importer in the following cases:

Deploy pods.

Pods restart for some reason.

Scale out the pods.

Thank you for the response. I have one more question: why is it necessary to include the Schema Importer in the pod? I'm considering the possibility of running the Schema Importer separately, outside of the pod.

@brfrn169
Thank you for your question!

In conclusion, I want to deploy ScalarDB Analytics with PostgreSQL as a Stateless workload to reduce maintenance costs and complex configurations, at the moment. This is why I run the Schema Importer as a sidecar in the pod.

For example, I want to avoid manually running the Schema Importer in the following cases.

Existing pods crash or restart

Scale pods (new pods start)

Challenges

ScalarDB Schema Loader and ScalarDL Schema Loader create database schemas (i.e., create some tables or objects) on the backend database side. In other words, those objects are persisted by the backend database. So, basically, ScalarDB/ScalarDL has no state in themselves.

However, Schema Importer creates some objects (e.g., foreign servers, extensions, and views) on the ScalarDB Analytics with PostgreSQL side. In other words, strictly, ScalarDB Analytics with PostgreSQL has states. It's a Stateful workload.

So, if the pod is restarted for some reason, the loaded objects are lost. In this case, we have to re-run Schema Importer to re-load all objects on the PostgreSQL.

As well as the pods restart, we have to run the Schema Importer if we scale out (add a new pod) to create some objects in the new pod (in the new PostgreSQL). This is because each pod (each PostgreSQL) has objects (e.g., views) respectively.

Solution 1 (make it Stateful workload)

To address the above challenges, we can deploy ScalarDB Analytics with PostgreSQL as a Stateful workload by using StatefulSet which is one of the Kubernetes resources.

In this case, the objects (foreign server, extension, and views) are stored and persisted in the PV (persistent volume) which is attached to the pod.

So, we don't need to re-run Schema Importer if the pods crash/restart. However, we still have to run Schema Importer manually when we scale out pods.

Also, in this solution, we have to use a bit more complex configurations for instance StatefulSet and PersistentVolume, rather than we deploy it as a Stateless workload by using Deployment. It takes maintenance costs.

In addition, in this case, we have to consider the backup/restore of the PersistentVolume. It increases operation costs.

So, I want to avoid this solution if I can.

Solution 2 (run Schema Importer manually every time)

This is a simple (but not easy) solution. We can deploy ScalarDB Analytics with PostgreSQL as a Stateless workload with Deployment, and run Schema Importer manually every time we need.

However, this solution increases the operation costs on the user side. And, this solution cannot take advantage of the self-healing (automatically pod restart when some failure occurs) feature of Kubernetes well.

Solution 3 (run Schema Importer as a sidecar / our choice)

To resolve the challenges with the smallest additional costs, we decided to run Schema Importer as a sidecar in the pod startup step.

In this case, the pod runs Schema Importer automatically when pods crash/restart or a new pod is added. So, we can avoid manually running Schema Importer.

Also, in this case, we don't need to store/persist some objects in the PersistentVolume because the pod runs Schema Importer every time on its startup. We can avoid additional costs to maintain the Stateful workload.

This is why I decided to run Schema Importer as a sidecar.

Sounds good! Thank you for the explanation!

kota2and3kan · 2023-11-15T07:33:05Z

charts/scalardb-analytics-postgresql/templates/scalardb-analytics-postgresql/deployment.yaml

+          - secretRef:
+              name:  "{{ .Values.scalardbAnalyticsPostgreSQL.postgresql.secretName }}"


We set the superuser's password of PostgreSQL via a Secret resource.

I prefer to use env because I don't know the key name that should be included in the secret from envFrom (although it is case by case).

Ah, I see. In this case, the environment variable name is fixed POSTGRES_PASSWORD. It depends on the PostgreSQL official container image.

In other words, users cannot use arbitrary environment variable names, and there is no special reason that I use envFrom here.

So, I will update to use env. Thank you for your suggestion!

Fixed in 8af1a27.

kota2and3kan · 2023-11-15T07:36:39Z

charts/scalardb-analytics-postgresql/templates/scalardb-analytics-postgresql/deployment.yaml

+            periodSeconds: 10
+            successThreshold: 1
+            timeoutSeconds: 1
+        - name: schema-importer


As I mentioned in the PR description, this chart run Schema Importer as a sidecar.

kota2and3kan · 2023-11-15T07:37:57Z

charts/scalardb-analytics-postgresql/templates/scalardb-analytics-postgresql/deployment.yaml

+        - configMap:
+            defaultMode: 0440
+            name: {{ include "scalardb-analytics-postgresql.fullname" . }}-database-properties
+          name: database-properties-volume


The ScalarDB Analytics with PostgreSQL container and Schema Importer container share the same database.properties file.

kota2and3kan · 2023-11-15T07:40:05Z

charts/scalardb-analytics-postgresql/values.schema.json

@@ -0,0 +1,239 @@
+{


This file is automatically generated based on the values.yaml file.

kota2and3kan · 2023-11-15T07:43:12Z

charts/scalardb-analytics-postgresql/values.yaml

+    # -- To work ScalarDB Analytics with PostgreSQL properly, you must set "201" to "podSecurityContext.fsGroup".
+    fsGroup: 201


To run the entorypoint.sh by scalar (UID=201) user in the Schema Importer container, we have to mount the entrypoint.sh file with 201:201 configuration as a file owner configuration. So, we have to set fsGroup=201 here.

kota2and3kan · 2023-11-15T07:46:06Z

charts/scalardb-analytics-postgresql/values.yaml

+    # -- Containers should be run as a non-root user with the minimum required permissions (principle of least privilege).
+    runAsNonRoot: true
+    # -- The PostgreSQL official image use the "postgres (UID=999)" user by default.
+    runAsUser: 999


The PostgreSQL container image sets non-root user postgres with UID=999. To run the container with the non-root user properly, we have to set UID=999 here.
https://github.com/scalar-labs/docker/blob/main/jdk-postgres/8-15/Dockerfile#L14

kota2and3kan · 2023-11-16T01:06:12Z

charts/scalardb-analytics-postgresql/Chart.yaml

+version: 1.0.0-SNAPSHOT
+appVersion: 3.10.3


At this time, ScalarDB Analytics with PostgreSQL does not release the SNAPSHOT version. So, I set the latest stable version.

However, we are working on releasing the SNAPSHOT version on the ScalarDB Analytics with PostgreSQL side. In the future, we will set the SNAPSHOT version here.

docs/configure-custom-values-scalardb-analytics-postgresql.md

Co-authored-by: Mitsunori Komatsu <[email protected]>

docs/configure-custom-values-scalardb-analytics-postgresql.md

Co-authored-by: Mitsunori Komatsu <[email protected]>

brfrn169

Overall, LGTM. Left several minor comments. Please take a look when you have time!

brfrn169 · 2023-11-20T01:24:58Z

charts/scalardb-analytics-postgresql/templates/scalardb-analytics-postgresql/configmap.yaml

+  entrypoint.sh: |
+    #!/bin/bash


So, this runs Schema Importer every time the pod starts?

brfrn169 · 2023-11-20T01:32:50Z

docs/configure-custom-values-scalardb-analytics-postgresql.md

+    scalar.db.storage=cassandra
+```
+
+### Namespaces configurations


This might cause confusion between ScalarDB's namespace and Kubernetes's namespace.

Ah, I see. I agree with that concern.
I will update the documents.
Thank you for pointing it out!

I updated the document to describe the namespace is the database namespace in this context explicitly in 831fa61.

kota2and3kan · 2023-11-20T10:25:23Z

@brfrn169
Thank you for your review!
I updated the documents and left an answer to your question.
Please take a look again when you have time!

Co-authored-by: Josh Wong <[email protected]>

feeblefakie

LGTM! Thank you!

brfrn169

LGTM! Thank you!

josh-wong

Looking good!👍 I've added some comments and suggestions, so PTAL!

docs/mount-files-or-volumes-on-scalar-pods.md

charts/scalardb-analytics-postgresql/values.yaml

docs/configure-custom-values-scalardb-analytics-postgresql.md

docs/how-to-deploy-scalardb-analytics-postgresql.md

Co-authored-by: Josh Wong <[email protected]>

kota2and3kan · 2023-11-28T10:02:17Z

@komamitsu @josh-wong
Thank you for your review!
I applied your suggestions.
Please take a look when you have time!

josh-wong

I left one minor suggestion for something that I didn't catch before. Other than that, LGTM! Thank you🙇‍♂️

charts/scalardb-analytics-postgresql/values.yaml

komamitsu

LGTM! 👍

Co-authored-by: Josh Wong <[email protected]>

choplin

Overall, it looks good to me! Thanks! I left several questions. I would appreciate it if you could take a look.

choplin · 2023-12-18T02:19:26Z

charts/scalardb-analytics-postgresql/README.md

@@ -0,0 +1,54 @@
+# scalardb-analytics-postgresql


Just curious. How is this file generated?

choplin · 2023-12-18T02:27:12Z

docs/configure-custom-values-scalardb-analytics-postgresql.md

+
+```yaml
+scalardbAnalyticsPostgreSQL:
+  replicaCount: 3


Does this setting create the Postgres instances with replication? Or does it just make multiple instances?

This setting just makes multiple instances without streaming replication or logical replication. At the moment, we cannot control the replication or HA feature of PostgreSQL by using this chart. We just deploy it as a single instance or multiple instances.

As I mentioned, we cannot control HA features, however, I think ScalarDB Analytics with PostgreSQL is basically a read-only product for the analytical workload. So, I don't think we need to use the replication feature at this time.

But, from the perspective of availability, I think we can make it more available by deploying 3 pods (ideally across on 3 zones in a cloud environment).

This is why I set 3 by default in this chart.

kota2and3kan

@choplin
Thank you for your review and questions!
I left answers. Please take a look when you have time!

kota2and3kan · 2023-12-18T02:36:10Z

charts/scalardb-analytics-postgresql/README.md

@@ -0,0 +1,54 @@
+# scalardb-analytics-postgresql


You can generate this file by using helm-docs.
https://github.com/norwoodj/helm-docs

Also, in our repository, you can run the helm-docs by using the following script.
https://github.com/scalar-labs/helm-charts/blob/main/scripts/update-chart-docs.sh

kota2and3kan · 2023-12-18T02:40:12Z

docs/configure-custom-values-scalardb-analytics-postgresql.md

+
+```yaml
+scalardbAnalyticsPostgreSQL:
+  replicaCount: 3


This setting just makes multiple instances without streaming replication or logical replication. At the moment, we cannot control the replication or HA feature of PostgreSQL by using this chart. We just deploy it as a single instance or multiple instances.

As I mentioned, we cannot control HA features, however, I think ScalarDB Analytics with PostgreSQL is basically a read-only product for the analytical workload. So, I don't think we need to use the replication feature at this time.

But, from the perspective of availability, I think we can make it more available by deploying 3 pods (ideally across on 3 zones in a cloud environment).

This is why I set 3 by default in this chart.

kota2and3kan added 2 commits November 7, 2023 17:26

Add new chart for ScalarDB Analytics with PostgreSQL

d47ed9a

Update CI for ScalarDB Analytics with PostgreSQL

e7800eb

kota2and3kan added documentation Improvements or additions to documentation enhancement New feature or request labels Nov 7, 2023

kota2and3kan self-assigned this Nov 7, 2023

kota2and3kan added 6 commits November 13, 2023 16:41

Merge branch 'main' into add-scalardb-analytics-postgresql-chart

a79142f

Use secret resource to set superuser password

19c8a1b

Update comment about entrypoint.sh in values.yaml

968c1d0

Remove trailing spaces

31892a9

Update probe to use "SELECT 1" instead of pg_isready

13636e2

Add documents of ScalarDB Analytics with PostgreSQL

72d18ce

kota2and3kan added the scalardb analytics postgresql PR for ScalarDB Analytics with PostgreSQL label Nov 15, 2023

kota2and3kan commented Nov 15, 2023

View reviewed changes

Add comment in values.yaml

d1c9874

kota2and3kan requested review from superbrothers, choplin, feeblefakie, josh-wong, komamitsu and brfrn169 November 15, 2023 08:00

kota2and3kan added 3 commits November 15, 2023 18:23

Apply imagePullPolicy to Schema Importer properly

dc16ec8

Fix wrong parameter name

4d96022

Update Chart.yaml

6ff3167

kota2and3kan commented Nov 16, 2023

View reviewed changes

komamitsu reviewed Nov 16, 2023

View reviewed changes

docs/configure-custom-values-scalardb-analytics-postgresql.md Outdated Show resolved Hide resolved

kota2and3kan requested a review from komamitsu November 16, 2023 04:21

komamitsu reviewed Nov 16, 2023

View reviewed changes

docs/configure-custom-values-scalardb-analytics-postgresql.md Outdated Show resolved Hide resolved

Update docs/configure-custom-values-scalardb-analytics-postgresql.md

f092b5e

Co-authored-by: Mitsunori Komatsu <[email protected]>

komamitsu reviewed Nov 16, 2023

View reviewed changes

docs/configure-custom-values-scalardb-analytics-postgresql.md Outdated Show resolved Hide resolved

Update docs/configure-custom-values-scalardb-analytics-postgresql.md

35cf76d

Co-authored-by: Mitsunori Komatsu <[email protected]>

superbrothers approved these changes Nov 19, 2023

View reviewed changes

brfrn169 reviewed Nov 20, 2023

View reviewed changes

kota2and3kan added 3 commits November 20, 2023 18:10

Use env to pass POSTGRES_PASSWORD instead of envFrom

8af1a27

Describe namespace is database namespace explicitly

831fa61

Fix CI error

ae85f82

kota2and3kan requested a review from brfrn169 November 20, 2023 10:24

Update docs/configure-custom-values-scalardb-analytics-postgresql.md

3183437

Co-authored-by: Josh Wong <[email protected]>

feeblefakie approved these changes Nov 21, 2023

View reviewed changes

brfrn169 approved these changes Nov 23, 2023

View reviewed changes

josh-wong requested changes Nov 27, 2023

View reviewed changes

kota2and3kan and others added 6 commits November 28, 2023 18:45

Apply suggestions from code review

de8b6d2

Co-authored-by: Josh Wong <[email protected]>

Apply suggestions from code review

fcb5a08

Co-authored-by: Josh Wong <[email protected]>

Apply suggestions from code review

a0e07b7

Co-authored-by: Josh Wong <[email protected]>

Apply suggestions from code review

5b102dc

Co-authored-by: Josh Wong <[email protected]>

Apply suggestions from code review

694a0dd

Co-authored-by: Josh Wong <[email protected]>

Update README based on review feedback

1e52981

kota2and3kan requested review from komamitsu and josh-wong November 28, 2023 10:02

josh-wong approved these changes Nov 28, 2023

View reviewed changes

charts/scalardb-analytics-postgresql/values.yaml Outdated Show resolved Hide resolved

komamitsu approved these changes Nov 28, 2023

View reviewed changes

kota2and3kan and others added 2 commits November 29, 2023 10:41

Update charts/scalardb-analytics-postgresql/values.yaml

2a8f86d

Co-authored-by: Josh Wong <[email protected]>

Update README based on review feedback

f4d52ef

choplin approved these changes Dec 18, 2023

View reviewed changes

kota2and3kan commented Dec 18, 2023

View reviewed changes

Merge branch 'main' into add-scalardb-analytics-postgresql-chart

e80062b

kota2and3kan merged commit b1e2190 into main Dec 18, 2023
14 checks passed

kota2and3kan deleted the add-scalardb-analytics-postgresql-chart branch December 18, 2023 04:42

josh-wong mentioned this pull request Dec 19, 2023

Add new and updated Helm Charts docs scalar-labs/docs-scalardb#109

Merged

6 tasks

		- secretRef:
		name: "{{ .Values.scalardbAnalyticsPostgreSQL.postgresql.secretName }}"

		# -- To work ScalarDB Analytics with PostgreSQL properly, you must set "201" to "podSecurityContext.fsGroup".
		fsGroup: 201

		version: 1.0.0-SNAPSHOT
		appVersion: 3.10.2

		version: 1.0.0-SNAPSHOT
		appVersion: 3.10.3

Add new chart for ScalarDB Analytics with PostgreSQL #242

Add new chart for ScalarDB Analytics with PostgreSQL #242

Conversation

kota2and3kan commented Nov 7, 2023 • edited Loading

Description

Related issues and/or PRs

Changes made

Checklist

Additional notes (optional)

Regarding getting started guide

Overview of what you need to run ScalarDB Analytics with PostgreSQL

How this chart deploy ScalarDB Analytics with PostgreSQL

Release notes

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Challenges

Solution 1 (make it Stateful workload)

Solution 2 (run Schema Importer manually every time)

Solution 3 (run Schema Importer as a sidecar / our choice)

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

brfrn169 left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kota2and3kan commented Nov 20, 2023

feeblefakie left a comment

Choose a reason for hiding this comment

brfrn169 left a comment

Choose a reason for hiding this comment

josh-wong left a comment

Choose a reason for hiding this comment

kota2and3kan commented Nov 28, 2023

josh-wong left a comment

Choose a reason for hiding this comment

komamitsu left a comment

Choose a reason for hiding this comment

choplin left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kota2and3kan left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kota2and3kan commented Nov 7, 2023 •

edited

Loading

Overview of what you need to run `ScalarDB Analytics with PostgreSQL`

How this chart deploy `ScalarDB Analytics with PostgreSQL`

Solution 1 (make it `Stateful` workload)