Update self-hosted deployment instructions #1 #888
+152
−58
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Sangram Rath <[email protected]>
✅ Deploy Preview for bejewelled-pegasus-b0ce81 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
sangramrath
requested review from
leecalcote
and removed request for
leecalcote
leecalcote
reviewed
Jan 15, 2026
| #### Installation | ||
|
|
||
| Layer5 offers on-premises installation of its [Meshery Remote Provider](https://docs.meshery.io/extensibility/providers): Layer5 Cloud. Contained in the [Layer5 Helm repository](https://docs.layer5.io/charts) is one chart with two subcharts (see repo [index](https://docs.layer5.io/charts/index.yaml)). | ||
| You will install the Postgres database first followed by Layer5 cloud. |
Member
There was a problem hiding this comment.
Suggested change
| You will install the Postgres database first followed by Layer5 cloud. | |
| You will install the Postgres database first or configure connection details to your existing Postgres v12+ database server, followed by the rest of Layer5 Cloud's containers. |
leecalcote
reviewed
Jan 15, 2026
| *You may chose to use an alternative ingress controller, but the following instructions assume the use of NGINX Ingress Controller.* | ||
| Deploying a PostgreSQL cluster requires the follwing pre-requisite resources: | ||
| - A super user secret | ||
| - A Meshery user secret |
Member
There was a problem hiding this comment.
I wonder if here, we might be be referring to the meshery database schema, so a Postges user/password?
leecalcote
reviewed
Jan 15, 2026
| Review and update values if necessary. If you have followed this tutorial with the exact steps, there are no changes requires to get started. | ||
|
|
||
| ## Uninstalling the Chart | ||
| 3. Deploy Layer5 cloud using the `helm install` command. |
Member
There was a problem hiding this comment.
Suggested change
| 3. Deploy Layer5 cloud using the `helm install` command. | |
| 3. Deploy Layer5 Cloud using the `helm install` command. |
leecalcote
reviewed
Jan 15, 2026
|
|
||
| ### Kubernetes-based Installation with Helm | ||
|
|
||
| Layer5 offers on-premises installation of its [Meshery Remote Provider](https://docs.meshery.io/extensibility/providers): Layer5 Cloud. Contained in the [Layer5 Helm repository](https://docs.layer5.io/charts) is one chart with two subcharts (see repo [index](https://docs.layer5.io/charts/index.yaml)). |
Member
There was a problem hiding this comment.
Suggested change
| Layer5 offers on-premises installation of its [Meshery Remote Provider](https://docs.meshery.io/extensibility/providers): Layer5 Cloud. Contained in the [Layer5 Helm repository](https://docs.layer5.io/charts) is one chart with two subcharts (see repo [index](https://docs.layer5.io/charts/index.yaml)). | |
| Layer5 offers on-premises installation of its [Meshery Remote Provider](https://docs.meshery.io/extensibility/providers): Layer5 Cloud. Available in the [Layer5 Helm repository](https://docs.layer5.io/charts) is the layer5-cloud chart, which contains two subcharts. See the Helm repo [index](https://docs.layer5.io/charts/index.yaml) for details. |
leecalcote
reviewed
Jan 15, 2026
|
|
||
| ##### 1. Create dedicated namespaces | ||
|
|
||
| This deployment uses two namespaces, `cnpg-postgres` for hosting the PostgreSQL database using CloudNativePG operator and `layer5-cloud` namespace for the Layer5 cloud. You can also choose to keep all components in the same namespace. |
Member
There was a problem hiding this comment.
Suggested change
| This deployment uses two namespaces, `cnpg-postgres` for hosting the PostgreSQL database using CloudNativePG operator and `layer5-cloud` namespace for the Layer5 cloud. You can also choose to keep all components in the same namespace. | |
| This deployment uses two namespaces, `cnpg-postgres` for hosting the PostgreSQL database using CloudNativePG operator and `layer5-cloud` namespace for the Layer5 Cloud. You can also choose to keep all components in the same namespace. |
Member
|
This is great! 😃 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Notes for Reviewers
This PR fixes #
Signed commits