From a33875fe028e608a730721262b9cbbb1ad27cd1e Mon Sep 17 00:00:00 2001 From: Beth Legesse Date: Thu, 23 May 2024 16:59:08 -0500 Subject: [PATCH 1/4] chore: info about dedicated postgres instance --- content/influxdb/clustered/install/prerequisites.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/influxdb/clustered/install/prerequisites.md b/content/influxdb/clustered/install/prerequisites.md index 65f46ea21..97d8b8822 100644 --- a/content/influxdb/clustered/install/prerequisites.md +++ b/content/influxdb/clustered/install/prerequisites.md @@ -23,6 +23,8 @@ We **strongly** recommend that you enable object versioning in your object store - **PostgreSQL-compatible database** _(AWS Aurora, hosted Postgres, etc.)_: Used to store the InfluxDB catalog - Supported PostgreSQL versions: **13.8–14.6** + - InfluxDB Clustered requires a dedicated PostgreSQL instance used exclusively for InfluxDB purposes to avoid conflicts. + - **OAuth 2.0 provider**: - Must support [Device Authorization Flow](https://auth0.com/docs/get-started/authentication-and-authorization-flow/device-authorization-flow) - Tested and supported providers: @@ -31,6 +33,10 @@ We **strongly** recommend that you enable object versioning in your object store - [Auth0](https://auth0.com/) - **TLS certificate**: for ingress to the cluster +### Namespace Recommendations +- **Separate Namespace (Recommended):** + - For better management and clarity, it is recommended to deploy the PostgreSQL instance and the Object Store (Parquet files) in a separate namespace from the rest of the InfluxDB components. + ## Set up a Kubernetes cluster 1. Deploy a Kubernetes cluster. You must Kubernetes v1.25 or higher. From b11c15ee84e64aba1a677a33e62c0d5eb9a20bd3 Mon Sep 17 00:00:00 2001 From: Beth Legesse Date: Thu, 23 May 2024 17:08:43 -0500 Subject: [PATCH 2/4] chore: fix --- content/influxdb/clustered/install/prerequisites.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/content/influxdb/clustered/install/prerequisites.md b/content/influxdb/clustered/install/prerequisites.md index 97d8b8822..e6f81045e 100644 --- a/content/influxdb/clustered/install/prerequisites.md +++ b/content/influxdb/clustered/install/prerequisites.md @@ -23,7 +23,7 @@ We **strongly** recommend that you enable object versioning in your object store - **PostgreSQL-compatible database** _(AWS Aurora, hosted Postgres, etc.)_: Used to store the InfluxDB catalog - Supported PostgreSQL versions: **13.8–14.6** - - InfluxDB Clustered requires a dedicated PostgreSQL instance used exclusively for InfluxDB purposes to avoid conflicts. + - Ensure that the PostgreSQL instance is dedicated exclusively to InfluxDB purposes to avoid conflicts. This prevents issues due to shared usage with other applications. - **OAuth 2.0 provider**: - Must support [Device Authorization Flow](https://auth0.com/docs/get-started/authentication-and-authorization-flow/device-authorization-flow) @@ -33,10 +33,6 @@ We **strongly** recommend that you enable object versioning in your object store - [Auth0](https://auth0.com/) - **TLS certificate**: for ingress to the cluster -### Namespace Recommendations -- **Separate Namespace (Recommended):** - - For better management and clarity, it is recommended to deploy the PostgreSQL instance and the Object Store (Parquet files) in a separate namespace from the rest of the InfluxDB components. - ## Set up a Kubernetes cluster 1. Deploy a Kubernetes cluster. You must Kubernetes v1.25 or higher. @@ -57,6 +53,8 @@ in a separate namespace from InfluxDB or external to Kubernetes entirely. Running the Catalog database and Object Store in a separate namespace or outside of Kubernetes makes management of the InfluxDB instance easier and helps to prevents accidental data loss. + +While deploying everything in the same namespace is possible for testing or initial setups, it is not recommended for production environments. {{% /note %}} ### Cluster sizing recommendation From a666f3faade9c252aceb2c431af7febaa9d6d207 Mon Sep 17 00:00:00 2001 From: Bethelhem Legesse Date: Tue, 28 May 2024 07:14:51 -0500 Subject: [PATCH 3/4] fix: Update content Co-authored-by: Scott Anderson --- content/influxdb/clustered/install/prerequisites.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/influxdb/clustered/install/prerequisites.md b/content/influxdb/clustered/install/prerequisites.md index e6f81045e..ccf4394a5 100644 --- a/content/influxdb/clustered/install/prerequisites.md +++ b/content/influxdb/clustered/install/prerequisites.md @@ -23,7 +23,7 @@ We **strongly** recommend that you enable object versioning in your object store - **PostgreSQL-compatible database** _(AWS Aurora, hosted Postgres, etc.)_: Used to store the InfluxDB catalog - Supported PostgreSQL versions: **13.8–14.6** - - Ensure that the PostgreSQL instance is dedicated exclusively to InfluxDB purposes to avoid conflicts. This prevents issues due to shared usage with other applications. + - Ensure that the PostgreSQL-compatible instance is dedicated exclusively to InfluxDB. This avoids conflicts and prevents issues caused by shared usage with other applications. - **OAuth 2.0 provider**: - Must support [Device Authorization Flow](https://auth0.com/docs/get-started/authentication-and-authorization-flow/device-authorization-flow) From 7d1d8ab46f780506dedebfc6721c8c3904652319 Mon Sep 17 00:00:00 2001 From: Bethelhem Legesse Date: Tue, 28 May 2024 07:15:18 -0500 Subject: [PATCH 4/4] fix: Update content Co-authored-by: Scott Anderson --- content/influxdb/clustered/install/prerequisites.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/influxdb/clustered/install/prerequisites.md b/content/influxdb/clustered/install/prerequisites.md index ccf4394a5..e35066aa0 100644 --- a/content/influxdb/clustered/install/prerequisites.md +++ b/content/influxdb/clustered/install/prerequisites.md @@ -54,7 +54,7 @@ Running the Catalog database and Object Store in a separate namespace or outside of Kubernetes makes management of the InfluxDB instance easier and helps to prevents accidental data loss. -While deploying everything in the same namespace is possible for testing or initial setups, it is not recommended for production environments. +While deploying everything in the same namespace is possible for testing or initial setup, it is not recommended for production environments. {{% /note %}} ### Cluster sizing recommendation