From a352bd308325e3a4b5fa64c1b0838d87c1fd526f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Onur=20Y=C4=B1lmaz?= Date: Wed, 1 Oct 2025 07:07:52 +0300 Subject: [PATCH 1/5] BE-7164 Add skeleton for the resource conf docs --- .../_apply-helm-configuration-changes.mdx | 8 +- .../helm-chart/configuration/index.md | 1 + .../configuration/resource-configuration.md | 88 +++++++++++++++++++ 3 files changed, 96 insertions(+), 1 deletion(-) create mode 100644 docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md diff --git a/docs/self-hosted-appcircle/install-server/helm-chart/configuration/_apply-helm-configuration-changes.mdx b/docs/self-hosted-appcircle/install-server/helm-chart/configuration/_apply-helm-configuration-changes.mdx index 2ecc99c8a..1f13ddd7e 100644 --- a/docs/self-hosted-appcircle/install-server/helm-chart/configuration/_apply-helm-configuration-changes.mdx +++ b/docs/self-hosted-appcircle/install-server/helm-chart/configuration/_apply-helm-configuration-changes.mdx @@ -1,7 +1,13 @@ To apply configuration changes to the Appcircle server installation, update the Helm release with the new configuration using the following command: :::info -The namespace, release name, and Helm repository name in the example command below are written for the example installation document. If you have changed these values while installing the Appcircle server, adjust the values if required. +The arguments used for the `helm upgrade` parameters in the sample command below are based on the installation document, and it is compatible with a default installation. + +- Release: `appcircle-server` +- Chart: `appcircle/appcircle` +- Namespace: `appcircle` + +If you have customized these values while installing the Appcircle server, change the values to your customized ones. ::: ```bash diff --git a/docs/self-hosted-appcircle/install-server/helm-chart/configuration/index.md b/docs/self-hosted-appcircle/install-server/helm-chart/configuration/index.md index 496fb16b4..a2706fb6a 100644 --- a/docs/self-hosted-appcircle/install-server/helm-chart/configuration/index.md +++ b/docs/self-hosted-appcircle/install-server/helm-chart/configuration/index.md @@ -22,5 +22,6 @@ Current headlines are listed below: - [Domain Verification](/self-hosted-appcircle/install-server/helm-chart/configuration/domain-verification) - [External Image Registries](/self-hosted-appcircle/install-server/helm-chart/configuration/external-image-registry) - [Advanced Configuration](/self-hosted-appcircle/install-server/helm-chart/configuration/advanced-configuration) +- [Resource Configuration](/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration) In order to see the details, check the submenu of this documentation page. diff --git a/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md b/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md new file mode 100644 index 000000000..6e900a614 --- /dev/null +++ b/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md @@ -0,0 +1,88 @@ +--- +title: Resource Configuration +description: Learn how to configure the resources of the Appcircle server using the Helm chart for production environments +tags: [self-hosted, helm, configuration, kubernetes, openshift] +sidebar_position: 120 +--- + +import NeedHelp from '@site/docs/\_need-help.mdx'; +import ApplyHelmConfigurationChanges from '@site/docs/self-hosted-appcircle/install-server/helm-chart/configuration/\_apply-helm-configuration-changes.mdx'; + +It's important that the Appcircle server services have enough resources to actually run in a Kubernetes or OpenShift cluster. Although the Appcircle server might work fine without setting any resource requests and limits using the default values, as a best practice, it's recommended to configure them for **production** workload and fine-tune the resources to fit your cluster resources when you need them. + +Setting the `resources.requests` and `resources.limits` for each service will allow Kubernetes or OpenShift to better dispatch the pods across the nodes. + +Following the guide here, you will learn how to configure "requests" and "limits" for the Appcircle server services to guarantee minimum resources for them in the **production** environment while preventing overconsumption with maximum thresholds. + +:::tip +If you are not familiar with the resource configuration concepts, you can get a quick overview from [here](https://cloud.google.com/blog/products/containers-kubernetes/kubernetes-best-practices-resource-requests-and-limits). +::: + +## Resource Requests and Limits + +The "requests" and "limits" define how much CPU and memory an Appcircle server service is guaranteed and allowed to use. + +- The "requests" ensures that the service always gets the minimum resources it needs. +- The "limits" covers the maximum usage to prevent overconsumption. + +Below is the table of services with their recommended "requests" and "limits" for **production** environments. + +Setting these, as guided below, improves the stability of production workloads while avoiding resource contention and keeping resource costs optimized, especially for shared clusters. + +| Service | Requests CPU | Requests Memory | Limits CPU | Limits memory | +| ------- | -------------- | ----------------- | ------------ | --------------- | +| `agentcache` | 20m | 512Mi | 100m | 1000Mi | +| `agentcache-redis` | 10m | 25Mi | 50m | 100Mi | +| `apigateway` | 400m | 800Mi | 1500m | 1200Mi | +| `apigateway-redis` | 10m | 25Mi | 50m | 100Mi | + + + +:::tip +Using the table above, you can also find out the total resource requirements of the Appcircle server for the **production** environment. + +Keep in mind that the "requests" and "limits" here are for one replica. When you have more than one replica, you need to **multiply them by the replica count** to see the whole picture. + +For the recommended replica counts, please refer to the details in the [Increase the Replica Counts](/self-hosted-appcircle/install-server/helm-chart/configuration/advanced-configuration#increase-the-replica-counts) section. +::: + +In the following section you can find the Helm chart details for the recommended configuration. You should update your `values.yaml` file using the relevant sections below. + +
+ Click to view the Helm chart values for the **requests** and **limits**. + +:::caution +Some keys might already exist in your `values.yaml` file that come from other configurations. + +Make sure to update existing ones instead of adding new ones for them to avoid duplicate keys. +::: + +```yaml +agentcache: + resources: + requests: + cpu: 20m + memory: 512Mi + limits: + cpu: 100m + memory: 1000Mi + agentcache-redis: + master: + resources: + requests: + cpu: 10m + memory: 25Mi + limits: + cpu: 50m + memory: 100Mi +``` + + + +
+ +## Applying Configuration Changes + + + + \ No newline at end of file From 800b940685e2fb7d38bf7d2b352e15c5de275a20 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Onur=20Y=C4=B1lmaz?= Date: Wed, 1 Oct 2025 07:25:25 +0300 Subject: [PATCH 2/5] BE-7164 Improvements for current state of docs --- .../configuration/resource-configuration.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md b/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md index 6e900a614..d59cfe352 100644 --- a/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md +++ b/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md @@ -8,11 +8,11 @@ sidebar_position: 120 import NeedHelp from '@site/docs/\_need-help.mdx'; import ApplyHelmConfigurationChanges from '@site/docs/self-hosted-appcircle/install-server/helm-chart/configuration/\_apply-helm-configuration-changes.mdx'; -It's important that the Appcircle server services have enough resources to actually run in a Kubernetes or OpenShift cluster. Although the Appcircle server might work fine without setting any resource requests and limits using the default values, as a best practice, it's recommended to configure them for **production** workload and fine-tune the resources to fit your cluster resources when you need them. +It's important that the Appcircle services have enough resources to actually run in a Kubernetes or OpenShift cluster. Although the Appcircle server might work fine without setting any resource "requests" and "limits" using the default values, as a best practice, it's recommended to configure them for **production** workload and fine-tune the resources to fit your cluster resources when you need them. -Setting the `resources.requests` and `resources.limits` for each service will allow Kubernetes or OpenShift to better dispatch the pods across the nodes. +Setting the `resources.requests` and `resources.limits` for each Appcircle service will allow Kubernetes or OpenShift to better dispatch the pods across the nodes. -Following the guide here, you will learn how to configure "requests" and "limits" for the Appcircle server services to guarantee minimum resources for them in the **production** environment while preventing overconsumption with maximum thresholds. +Following the guide here, you will learn how to configure "requests" and "limits" for the Appcircle server to guarantee minimum resources for the services in the **production** environment while preventing overconsumption with maximum thresholds. :::tip If you are not familiar with the resource configuration concepts, you can get a quick overview from [here](https://cloud.google.com/blog/products/containers-kubernetes/kubernetes-best-practices-resource-requests-and-limits). @@ -20,16 +20,16 @@ If you are not familiar with the resource configuration concepts, you can get a ## Resource Requests and Limits -The "requests" and "limits" define how much CPU and memory an Appcircle server service is guaranteed and allowed to use. +The "requests" and "limits" define how much CPU and memory an Appcircle service is guaranteed and allowed to use. - The "requests" ensures that the service always gets the minimum resources it needs. - The "limits" covers the maximum usage to prevent overconsumption. -Below is the table of services with their recommended "requests" and "limits" for **production** environments. +Below is the table of Appcircle services with their recommended "requests" and "limits" for **production** environments. Setting these, as guided below, improves the stability of production workloads while avoiding resource contention and keeping resource costs optimized, especially for shared clusters. -| Service | Requests CPU | Requests Memory | Limits CPU | Limits memory | +| | Requests CPU | Requests Memory | Limits CPU | Limits Memory | | ------- | -------------- | ----------------- | ------------ | --------------- | | `agentcache` | 20m | 512Mi | 100m | 1000Mi | | `agentcache-redis` | 10m | 25Mi | 50m | 100Mi | @@ -41,7 +41,7 @@ Setting these, as guided below, improves the stability of production workloads w :::tip Using the table above, you can also find out the total resource requirements of the Appcircle server for the **production** environment. -Keep in mind that the "requests" and "limits" here are for one replica. When you have more than one replica, you need to **multiply them by the replica count** to see the whole picture. +Keep in mind that the "requests" and "limits" here are for **one replica**. When you have more than one replica, you need to **multiply them by the replica count** to see the whole picture. For the recommended replica counts, please refer to the details in the [Increase the Replica Counts](/self-hosted-appcircle/install-server/helm-chart/configuration/advanced-configuration#increase-the-replica-counts) section. ::: From 4335caf2a82864617066cc90f58dad2fc425f1fa Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Onur=20Y=C4=B1lmaz?= Date: Thu, 2 Oct 2025 06:19:00 +0300 Subject: [PATCH 3/5] BE-7164 Table and yaml complete --- .../configuration/resource-configuration.md | 472 ++++++++++++++++++ 1 file changed, 472 insertions(+) diff --git a/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md b/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md index d59cfe352..908046780 100644 --- a/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md +++ b/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md @@ -35,9 +35,60 @@ Setting these, as guided below, improves the stability of production workloads w | `agentcache-redis` | 10m | 25Mi | 50m | 100Mi | | `apigateway` | 400m | 800Mi | 1500m | 1200Mi | | `apigateway-redis` | 10m | 25Mi | 50m | 100Mi | +| `appparser` | 50m | 650Mi | 200m | 1500Mi | +| `auth-keycloak` | 250m | 1280Mi | 600m | 2000Mi | +| `build` | 100m | 850Mi | 300m | 1500Mi | +| `build-redis` | 10m | 25Mi | 50m | 100Mi | +| `distribution-server` | 100m | 720Mi | 250m | 1200Mi | +| `distribution-server-redis` | 10m | 25Mi | 50m | 100Mi | +| `distribution-testeradmin` | 50m | 410Mi | 200m | 600Mi | +| `distribution-testerapi` | 50m | 750Mi | 200m | 1300Mi | +| `distribution-testerapi-redis` | 10m | 25Mi | 50m | 100Mi | +| `distribution-testerweb` | 50m | 300Mi | 200m | 400Mi | +| `distribution-testerweb-redis` | 10m | 25Mi | 50m | 100Mi | +| `kafka` | 300m | 2000Mi | 1500m | 3000Mi | +| `license` | 50m | 260Mi | 200m | 320Mi | +| `license-redis` | 10m | 25Mi | 50m | 100Mi | +| `notification` | 50m | 300Mi | 200m | 450Mi | +| `otp` | 50m | 75Mi | 200m | 120Mi | +| `otp-redis` | 10m | 25Mi | 50m | 100Mi | +| `publish` | 50m | 380Mi | 200m | 720Mi | +| `publish-redis` | 10m | 25Mi | 50m | 100Mi | +| `reporting` | 50m | 320Mi | 200m | 400Mi | +| `resign` | 50m | 150Mi | 200m | 220Mi | +| `resource` | 50m | 1000Mi | 200m | 1500Mi | +| `resource-redis` | 10m | 25Mi | 50m | 100Mi | +| `schedulemanager` | 50m | 270Mi | 200m | 350Mi | +| `schedulemanager-redis` | 10m | 25Mi | 50m | 100Mi | +| `signingidentity` | 50m | 460Mi | 200m | 600Mi | +| `signingidentity-redis` | 10m | 25Mi | 50m | 100Mi | +| `store-admin` | 50m | 240Mi | 200m | 350Mi | +| `store-api` | 50m | 330Mi | 200m | 420Mi | +| `store-api-redis` | 10m | 25Mi | 50m | 100Mi | +| `store-profile` | 50m | 380Mi | 200m | 450Mi | +| `store-report` | 50m | 300Mi | 200m | 400Mi | +| `store-web` | 50m | 340Mi | 200m | 450Mi | +| `store-web-redis` | 10m | 25Mi | 50m | 100Mi | +| `storesubmit` | 50m | 265Mi | 200m | 350Mi | +| `storesubmit-redis` | 10m | 25Mi | 50m | 100Mi | +| `taskserver` | 50m | 135Mi | 200m | 200Mi | +| `taskserver-redis` | 10m | 25Mi | 50m | 100Mi | +| `vault` | 40m | 200Mi | 200m | 650Mi | +| `web-app` | 8m | 80Mi | 60m | 150Mi | +| `web-event` | 50m | 110Mi | 200m | 300Mi | +| `web-redis` | 10m | 25Mi | 50m | 100Mi | +| `webeventredis-master` | 100m | 1000Mi | 500m | 2000Mi | +| `webeventredis-replica` | 100m | 1000Mi | 500m | 2000Mi | +| `webhook` | 50m | 210Mi | 200m | 350Mi | + + + + + + :::tip Using the table above, you can also find out the total resource requirements of the Appcircle server for the **production** environment. @@ -75,6 +126,427 @@ agentcache: limits: cpu: 50m memory: 100Mi + +apigateway: + resources: + requests: + cpu: 400m + memory: 800Mi + limits: + cpu: 1500m + memory: 1200Mi + apigateway-redis: + master: + resources: + requests: + cpu: 10m + memory: 25Mi + limits: + cpu: 50m + memory: 100Mi + +appparser: + resources: + requests: + cpu: 50m + memory: 650Mi + limits: + cpu: 200m + memory: 1500Mi + +auth: + auth-keycloak: + resources: + requests: + cpu: 250m + memory: 1280Mi + limits: + cpu: 600m + memory: 2000Mi + +build: + resources: + requests: + cpu: 100m + memory: 850Mi + limits: + cpu: 300m + memory: 1500Mi + build-redis: + master: + resources: + requests: + cpu: 10m + memory: 25Mi + limits: + cpu: 50m + memory: 100Mi + +distribution: + distribution-server: + resources: + requests: + cpu: 100m + memory: 720Mi + limits: + cpu: 250m + memory: 1200Mi + distribution-server-redis: + master: + resources: + requests: + cpu: 10m + memory: 25Mi + limits: + cpu: 50m + memory: 100Mi + distribution-testeradmin: + resources: + requests: + cpu: 50m + memory: 410Mi + limits: + cpu: 200m + memory: 600Mi + distribution-testerapi: + resources: + requests: + cpu: 50m + memory: 750Mi + limits: + cpu: 200m + memory: 1300Mi + distribution-testerapi-redis: + master: + resources: + requests: + cpu: 10m + memory: 25Mi + limits: + cpu: 50m + memory: 100Mi + distribution-testerweb: + resources: + requests: + cpu: 50m + memory: 300Mi + limits: + cpu: 200m + memory: 400Mi + distribution-testerweb-redis: + master: + resources: + requests: + cpu: 10m + memory: 25Mi + limits: + cpu: 50m + memory: 100Mi + +kafka: + controller: + resources: + requests: + cpu: 300m + memory: 2000Mi + limits: + cpu: 1500m + memory: 3000Mi + +license: + resources: + requests: + cpu: 50m + memory: 260Mi + limits: + cpu: 200m + memory: 320Mi + license-redis: + master: + resources: + requests: + cpu: 10m + memory: 25Mi + limits: + cpu: 50m + memory: 100Mi + +notification: + resources: + requests: + cpu: 50m + memory: 300Mi + limits: + cpu: 200m + memory: 450Mi + +otp: + resources: + requests: + cpu: 50m + memory: 75Mi + limits: + cpu: 200m + memory: 120Mi + otp-redis: + master: + resources: + requests: + cpu: 10m + memory: 25Mi + limits: + cpu: 50m + memory: 100Mi + +publish: + resources: + requests: + cpu: 50m + memory: 380Mi + limits: + cpu: 200m + memory: 720Mi + publish-redis: + master: + resources: + requests: + cpu: 10m + memory: 25Mi + limits: + cpu: 50m + memory: 100Mi + +reporting: + resources: + requests: + cpu: 50m + memory: 320Mi + limits: + cpu: 200m + memory: 400Mi + +resign: + resources: + requests: + cpu: 50m + memory: 150Mi + limits: + cpu: 200m + memory: 220Mi + +resource: + resources: + requests: + cpu: 50m + memory: 1000Mi + limits: + cpu: 200m + memory: 1500Mi + resource-redis: + master: + resources: + requests: + cpu: 10m + memory: 25Mi + limits: + cpu: 50m + memory: 100Mi + +schedulemanager: + resources: + requests: + cpu: 50m + memory: 270Mi + limits: + cpu: 200m + memory: 350Mi + schedulemanager-redis: + master: + resources: + requests: + cpu: 10m + memory: 25Mi + limits: + cpu: 50m + memory: 100Mi + +signingidentity: + resources: + requests: + cpu: 50m + memory: 460Mi + limits: + cpu: 200m + memory: 600Mi + signingidentity-redis: + master: + resources: + requests: + cpu: 10m + memory: 25Mi + limits: + cpu: 50m + memory: 100Mi + +store: + store-web: + resources: + requests: + cpu: 50m + memory: 340Mi + limits: + cpu: 200m + memory: 450Mi + store-web-redis: + master: + resources: + requests: + cpu: 10m + memory: 25Mi + limits: + cpu: 50m + memory: 100Mi + store-admin: + resources: + requests: + cpu: 50m + memory: 240Mi + limits: + cpu: 200m + memory: 350Mi + store-api: + resources: + requests: + cpu: 50m + memory: 330Mi + limits: + cpu: 200m + memory: 420Mi + store-api-redis: + master: + resources: + requests: + cpu: 10m + memory: 25Mi + limits: + cpu: 50m + memory: 100Mi + store-profile: + resources: + requests: + cpu: 50m + memory: 380Mi + limits: + cpu: 200m + memory: 450Mi + store-report: + resources: + requests: + cpu: 50m + memory: 300Mi + limits: + cpu: 200m + memory: 400Mi + +storesubmit: + resources: + requests: + cpu: 50m + memory: 265Mi + limits: + cpu: 200m + memory: 350Mi + storesubmit-redis: + master: + resources: + requests: + cpu: 10m + memory: 25Mi + limits: + cpu: 50m + memory: 100Mi + +taskserver: + resources: + requests: + cpu: 50m + memory: 135Mi + limits: + cpu: 200m + memory: 200Mi + taskserver-redis: + master: + resources: + requests: + cpu: 10m + memory: 25Mi + limits: + cpu: 50m + memory: 100Mi + +vault: + server: + resources: + requests: + cpu: 40m + memory: 200Mi + limits: + cpu: 200m + memory: 650Mi + +web: + web-app: + resources: + requests: + cpu: 8m + memory: 80Mi + limits: + cpu: 60m + memory: 150Mi + web-event: + resources: + requests: + cpu: 50m + memory: 110Mi + limits: + cpu: 200m + memory: 300Mi + web-redis: + master: + resources: + requests: + cpu: 10m + memory: 25Mi + limits: + cpu: 50m + memory: 100Mi + +webeventredis: + master: + resources: + requests: + cpu: 100m + memory: 1000Mi + limits: + cpu: 500m + memory: 2000Mi + replica: + resources: + requests: + cpu: 100m + memory: 1000Mi + limits: + cpu: 500m + memory: 2000Mi + +webhook: + resources: + requests: + cpu: 50m + memory: 210Mi + limits: + cpu: 200m + memory: 350Mi ``` From eb46b9181f5634cfacaa5b3cfdf2496683589868 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Onur=20Y=C4=B1lmaz?= Date: Thu, 2 Oct 2025 06:41:28 +0300 Subject: [PATCH 4/5] BE-7164 Add info box for doc scope --- .../configuration/resource-configuration.md | 20 +++++++++++++++---- 1 file changed, 16 insertions(+), 4 deletions(-) diff --git a/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md b/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md index 908046780..531bd3aec 100644 --- a/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md +++ b/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md @@ -18,6 +18,22 @@ Following the guide here, you will learn how to configure "requests" and "limits If you are not familiar with the resource configuration concepts, you can get a quick overview from [here](https://cloud.google.com/blog/products/containers-kubernetes/kubernetes-best-practices-resource-requests-and-limits). ::: +:::info + +This document contains the Appcircle services, which are included in the "**Appcircle Server**" box in the [Kubernetes/OpenShift Architecture Using Helm Chart](/self-hosted-appcircle/install-server/helm-chart/configuration/production-readiness) diagram, and it is based on a **[production readiness](/self-hosted-appcircle/install-server/helm-chart/configuration/production-readiness)** setup. + +Therefore, it does not include resource requirements for the **[external services](/self-hosted-appcircle#kubernetesopenshift-architecture-using-helm-chart)** since they are documented in their own sections in detail considering the **production** requirements. + +When you install the Appcircle Helm chart with the default configuration and deploy all the required services to the cluster for testing or trial purposes, there will be some other services that are not within the scope of this document. These are recommended to be outside of the "**Appcircle Server**" box. + +- `auth-postgresql` +- `minio` +- `mongodb` + +One exception for that is the [HashiCorp Vault](/self-hosted-appcircle/install-server/helm-chart/configuration/production-readiness/database-and-vault#hashicorp-vault) service. Since it has a recommended **production** option as [External Data Store](/self-hosted-appcircle/install-server/helm-chart/configuration/production-readiness/database-and-vault#external-data-store-eg-mssql), you have an option to deploy the `vault` service to the cluster within the "**Appcircle Server**" box. You can find its resource requirements for this kind of setup in the following sections. + +::: + ## Resource Requests and Limits The "requests" and "limits" define how much CPU and memory an Appcircle service is guaranteed and allowed to use. @@ -81,10 +97,6 @@ Setting these, as guided below, improves the stability of production workloads w | `webeventredis-replica` | 100m | 1000Mi | 500m | 2000Mi | | `webhook` | 50m | 210Mi | 200m | 350Mi | - - - - From 966c10c788d0bb72c2bfd3c1f6cb3f06456e7c4f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Onur=20Y=C4=B1lmaz?= Date: Thu, 2 Oct 2025 06:50:50 +0300 Subject: [PATCH 5/5] BE-7164 Fix links and improve info box --- .../helm-chart/configuration/resource-configuration.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md b/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md index 531bd3aec..5069e3390 100644 --- a/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md +++ b/docs/self-hosted-appcircle/install-server/helm-chart/configuration/resource-configuration.md @@ -20,9 +20,9 @@ If you are not familiar with the resource configuration concepts, you can get a :::info -This document contains the Appcircle services, which are included in the "**Appcircle Server**" box in the [Kubernetes/OpenShift Architecture Using Helm Chart](/self-hosted-appcircle/install-server/helm-chart/configuration/production-readiness) diagram, and it is based on a **[production readiness](/self-hosted-appcircle/install-server/helm-chart/configuration/production-readiness)** setup. +This document contains the Appcircle services, which are included in the "**Appcircle Server**" box in the [Kubernetes/OpenShift Architecture Using Helm Chart](/self-hosted-appcircle#kubernetesopenshift-architecture-using-helm-chart) diagram, and it is based on a **production** setup. -Therefore, it does not include resource requirements for the **[external services](/self-hosted-appcircle#kubernetesopenshift-architecture-using-helm-chart)** since they are documented in their own sections in detail considering the **production** requirements. +Therefore, it does not include resource requirements for the **[external services](/self-hosted-appcircle/install-server/helm-chart/configuration/production-readiness)** since they are documented in their own sections in detail considering the **production** requirements. When you install the Appcircle Helm chart with the default configuration and deploy all the required services to the cluster for testing or trial purposes, there will be some other services that are not within the scope of this document. These are recommended to be outside of the "**Appcircle Server**" box. @@ -30,7 +30,7 @@ When you install the Appcircle Helm chart with the default configuration and dep - `minio` - `mongodb` -One exception for that is the [HashiCorp Vault](/self-hosted-appcircle/install-server/helm-chart/configuration/production-readiness/database-and-vault#hashicorp-vault) service. Since it has a recommended **production** option as [External Data Store](/self-hosted-appcircle/install-server/helm-chart/configuration/production-readiness/database-and-vault#external-data-store-eg-mssql), you have an option to deploy the `vault` service to the cluster within the "**Appcircle Server**" box. You can find its resource requirements for this kind of setup in the following sections. +One exception for that is the [HashiCorp Vault](/self-hosted-appcircle/install-server/helm-chart/configuration/production-readiness/database-and-vault#hashicorp-vault) service. Since it has a recommended **production** option as [External Data Store](/self-hosted-appcircle/install-server/helm-chart/configuration/production-readiness/database-and-vault#external-data-store-eg-mssql), you have an option to deploy the `vault` service to the cluster within the "**Appcircle Server**" box. You can find its resource requirements for this kind of setup in the following sections. You should ignore it if you are using the `vault` as an [External Vault Service](/self-hosted-appcircle/install-server/helm-chart/configuration/production-readiness/database-and-vault#external-vault-service). :::