Merge pull request #104 from packagist/clarify-multi-node-kubernetes-usage

Clarify that multi-node setup can't be used with built-in services

Author: IgorBenko

docs/self-hosted/kubernetes-embedded.md

@@ -37,6 +37,8 @@ in an existing Kubernetes cluster using Helm follow [this guide](./kubernetes-he
   * s3.kurl.sh (required to install the kots CLI)
   * amazonaws.com (required to install the kots CLI)
 
+
+
 <!-- See https://docs.replicated.com/enterprise/installing-general-requirements and https://kurl.sh/docs/install-with-kurl/system-requirements -->
 
 ## Installation
@@ -82,6 +84,11 @@ you can download it from https://packagist.com.
 ![Upload License](/Resources/public/img/docs/self-hosted-kubernetes/console-license.png)
 
 #### Configure Private Packagist Self-Hosted
+
+> Please note that the built-in services (PostgreSQL, MinIO, Redis) are meant to be used with a single-node setup only, because these options rely on local file storage.
+> Consult the documentation of your Cloud Provider what managed services can replace the built-in services
+> (eg. for AWS RDS, S3 and ElastiCache)
+
 The configuration screen is where you can set up the domains used for Private Packagist and the email configuration. It
 is also the place where you can configure if Private Packagist should use an existing Redis, PostgreSQL, or blob storage.
 ![Configuration](/Resources/public/img/docs/self-hosted-kubernetes/console-configure-application.png)