thanks for starting this, @matifali (and for reporting, @sharkymark! )

I tried setting up a quick (it ended up not being quick 😭 ) 3-node kubernetes cluster and ran through without errors, so I think a breakdown of the commands should be alright.

@sharkymark , if this feels like an alright solution, I'll edit the copy and we can merge it

@EdwardAngert - i think the simpler fix here is to set the URL as

postgres://coder:[email protected]:5432/coder?sslmode=disable

thoughts?

Hi @ericpaulsen! I tested this earlier and when using helm install coder-db bitnami/postgresql, the Bitnami chart creates a service named coder-db-postgresql, not coder-db.

Here's what I verified:

• helm install coder-db bitnami/postgresql → Service: coder-db-postgresql
• helm install postgresql bitnami/postgresql → Service: postgresql

The service naming follows the pattern {release-name}-postgresql (unless the release name already contains "postgresql").

Are you thinking of a different approach, or did you find that coder-db service exists in addition to coder-db-postgresql? I'd be happy to test any specific scenario you have in mind!

@ericpaulsen

@EdwardAngert - i think the simpler fix here is to set the URL as

postgres://coder:[email protected]:5432/coder?sslmode=disable

thoughts?

I'm super unfamiliar with kubernetes and helm, so I defer to you and @sharkymark.

If all we need to do is remove coder-db from the examples to make it work both as a proof-of-concept and for use cases like @sharkymark's (CI?) then I prefer more universally applicable examples--my goal is to make the examples in the docs work without too much modification, regardless of what docs examples the user started with and goes on to.

so

L47:

- helm install coder-db bitnami/postgresql \
+ helm install postgresql bitnami/postgresql \

L58:

- postgres://coder:[email protected]:5432/coder?sslmode=disable
+ postgres://coder:[email protected]:5432/coder?sslmode=disable

LL80-81:

kubectl create secret generic coder-db-url -n coder \
-  --from-literal=url="postgres://coder:[email protected]:5432/coder?sslmode=disable"
+  --from-literal=url="postgres://coder:[email protected]:5432/coder?sslmode=disable"

would that work?

That's a great approach @EdwardAngert! Using postgresql as the release name is indeed more universal and simpler. It eliminates the confusion entirely by making the service name match the most intuitive expectation.

Your suggested changes would:
✅ Make the examples work out-of-the-box for most users
✅ Eliminate the need for explanatory notes about service naming
✅ Use the most straightforward release name

I'll update the PR to implement these changes instead of the current approach. This is definitely cleaner!

✅ Changes implemented!

I've updated the PR to implement @EdwardAngert's suggested approach:

Changes made:

• helm install coder-db bitnami/postgresql → helm install postgresql bitnami/postgresql
• coder-db-postgresql.coder.svc.cluster.local → postgresql.coder.svc.cluster.local
• Removed all explanatory notes (no longer needed)

This is much cleaner and eliminates the confusion entirely. The examples now work out-of-the-box with the most intuitive service name. Thanks for the great suggestion! 🎉