From d0df6e4788051521e3432ffa60cb9b52392ae595 Mon Sep 17 00:00:00 2001 From: evyatarmeged Date: Mon, 6 May 2024 19:02:22 +0300 Subject: [PATCH] fixup --- docs/features/postgresql/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/features/postgresql/index.mdx b/docs/features/postgresql/index.mdx index 0c94305da..9355e2e12 100644 --- a/docs/features/postgresql/index.mdx +++ b/docs/features/postgresql/index.mdx @@ -34,7 +34,7 @@ To learn how to use the Intents Operator and Credentials Operator to enforce acc ### How does Otterize work with PostgreSQL? -The Otterize credentials operator a unique PostgreSQL username-password combination for each service's use, exposed via a Kubernetes Secret. The service will use these credentials to connect to the database. `ClientIntents` will define the access required by that service. As the intents are applied, The Otterize intents operator will keep the database's list of users and GRANTs up to date so that the service is able to access it. +The Otterize credentials operator will create a unique PostgreSQL username-password combination for each service's use, exposed via a Kubernetes Secret. The service will use these credentials to connect to the database. `ClientIntents` will define the access required by that service. As the intents are applied, The Otterize intents operator will keep the database's list of users and GRANTs up to date so that the service is able to access it. 1. To get started, your cluster must have Otterize deployed. 2. You'll need to create a `PostgreSQLServerConfig` in your cluster, providing a connection URL and admin-level credentials for Otterize to manage permissions in your database. Below is an example `PostgreSQLServerConfig` resource.