Skip to content

docs: enhance PostgreSQL demo guide with external connection and stor… #64

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
KUASWoodyLIN merged 1 commit into from
Jan 7, 2026
Merged

docs: enhance PostgreSQL demo guide with external connection and stor… #64

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion src/content/docs/demos/05-postgres.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,13 +45,23 @@ We'll be using the PostgreSQL Helm chart from [Bitnami Charts](https://artifacth

3. After uploading, navigate to the `Applications Store` to deploy the Helm chart.

**To allow external connections**, configure the service as NodePort in the deployment settings:
**To allow external connections and configure storage**, adjust the deployment settings:
```yaml
service:
type: NodePort
port: 5432
nodePort: 30432 # Port range: 30000-32767
primary:
persistence:
size: 10Gi # PVC Storage Request for PostgreSQL volume (e.g., 10Gi, 20Gi, 100Gi)
```

**Configuration Details**:
- **service.type**: Set to `NodePort` to allow external connections
- **service.port**: PostgreSQL service port (default: 5432)
- **service.nodePort**: External port accessible from outside the cluster
Copy link

@gemini-code-assist gemini-code-assist bot Jan 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To prevent potential user issues, it's helpful to mention that the specified nodePort might already be in use and that they may need to select a different one within the valid range. This proactive guidance can save users from troubleshooting a common deployment issue.

- **service.nodePort**: External port accessible from outside the cluster. If port 30432 is in use, choose another from the 30000-32767 range.

- **primary.persistence.size**: Storage size for the PostgreSQL data volume (adjust based on your needs)
Copy link

@gemini-code-assist gemini-code-assist bot Jan 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For better clarity and technical accuracy, it would be good to explicitly mention that this setting configures the size of the Persistent Volume Claim (PVC). This helps users connect the configuration to the underlying Kubernetes concepts and provides more precise documentation.

- **primary.persistence.size**: Storage size for the Persistent Volume Claim (PVC) for the PostgreSQL data volume (adjust based on your needs)


After deployment, you can connect externally using `<node_ip>:<nodePort>`.

4. Retrieve the PostgreSQL password from `Applications Secrets`:
Expand Down
Loading