Skip to content
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

Jump to bottom

Add explanation for username and password secret in PGSQL tutorial #195

Merged
merged 1 commit into from
Feb 5, 2024
Merged

Add explanation for username and password secret in PGSQL tutorial #195

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.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
14 changes: 12 additions & 2 deletions docs/quickstart/access-control/postgres.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,9 +62,18 @@ We will be using it to create a proxy to connect our locally running database to

# Tutorial

### Deploy the cluster
### Deploy tutorial services and request database credentials
This will set up the namespace we will use for our tutorial and deploy the client, server, and database.

This will set up the namespace we will use for our tutorial and deploy the cluster with our client, server, and database.
Our server's Deployment spec will specify an annotation on the Pod, which requests that the credentials operator will provision a username and password for the server.
```yaml
template:
metadata:
annotations:
credentials-operator.otterize.com/user-password-secret-name: server-creds
```
This specifies that the secret `server-creds` will have keys with the username and password to connect to the database.
The secret will only be created once the database is integrated with Otterize Cloud.

``` shell
kubectl create namespace otterize-tutorial-postgres
Expand Down Expand Up @@ -113,6 +122,7 @@ After providing a cluster name and environment. For this tutorial, choose:
3. Copy and run the Helm upgrade command.
4. You should see the Connection status change.


### View logs for the server
After the client, server, and database are up and running, we can see that the server does not have the appropriate access to the database by inspecting the logs with the following command.

Expand Down