mirror of
https://github.com/open-metadata/OpenMetadata.git
synced 2025-11-03 20:19:31 +00:00
60ff64c8ed
* Add changes for kubernetes deployment docs * Update Quickstart docker guide * fix: docker quickstart docs * Add troubleshooting guide for quickstart k8s * fix typo * upper case the placeholders * Add FAQs and update EKS deployment docs * fix: docs links * Update Deployment page * fix: update k8s gke docs * fix(chore): Notes as warning type * fix(chore): markdown link and typo * fix(refactor): Docker Deployment Docs * fix(refactor): Docker Deployment Docs * fix: upgrade k8s docs * fix(reviews): remove apache mod_proxy * fix(refactor): docker volumes docs section * fix(refactor): Code Review changes * Merge remote-tracking branch 'origin/main' into 12608 * Add troubleshoot docs for psql create extension pgcypto issue * fix: k8s docs with elasticsearch auth enabled * fix: Update the changes to v1.1.1 docs * fix: updated the docs for 1.1.1 * Add docker and kubernetes v1.1.1 changes in docs * fix: Docker Deployment Link * fix: more fixes --------- Co-authored-by: Akash-Jain <Akash.J@deuexsolutions.com>
9 lines
529 B
Markdown
9 lines
529 B
Markdown
## Minimum Sizing Requirements
|
|
|
|
We recommend you to allocate openmetadata-server with minimum of 2vCPUs and 6 GiB Memory.
|
|
|
|
For External Services that openmetadata depends on -
|
|
- For the database, minimum 2 vCPUs and 2 GiB RAM (per instance) with 30 GiB of Storage Volume Attached (dynamic expansion up to 100 GiB)
|
|
- For Elasticsearch, minimum 2 vCPUs and 2 GiB RAM (per instance) with 30 GiB of Storage volume attached
|
|
|
|
These settings apply as well when using managed instances, such as AWS RDS or GCP CloudSQL or AWS OpenSearch. |