You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/self-hosted/kubernetes-helm.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,17 +2,17 @@
2
2
##
3
3
4
4
The Private Packagist Self-Hosted Helm chart allows you to install Private Packagist in an existing Kubernetes cluster,
5
-
to instead install Private Packagist Self-Hosted without an existing Kubernetes cluster follow [this guide](./kubernetes-embedded.md).
5
+
to instead install Private Packagist Self-Hosted without an existing Kubernetes cluster, follow [this guide](./kubernetes-embedded.md).
6
6
7
7
## General requirements
8
8
9
9
1. A Kubernetes cluster v1.23 or newer
10
-
1. Your username and password to log in to the Helm registry on registry.replicated.com. You can find your credentials with your Private Packagist account onhttps://packagist.com. Don't have one yet? [Sign up for a free trial license!](https://packagist.com/self-hosted)
10
+
1. Your username and password to log in to the Helm registry on registry.replicated.com. You can find your credentials in your Private Packagist account athttps://packagist.com. Don't have one yet? [Sign up for a free trial license!](https://packagist.com/self-hosted)
11
11
1. One (sub-)domain to operate the web interface, e.g. packagist.myintranet.com
12
12
1. One (sub-)domain to operate the composer repository, e.g. repo.packagist.myintranet.com or packagist-repo.myintranet.com
13
13
1. An SSL certificate valid for both chosen domains
14
14
1. An SMTP server or a GMail account for Private Packagist Self-Hosted to send email
15
-
1. If your firewall restricts external connections the following domains must be accessible from the server:
15
+
1. If your firewall restricts external connections then the following domains must be accessible from the server:
16
16
* hub.docker.com
17
17
* proxy.replicated.com
18
18
* registry.replicated.com
@@ -26,13 +26,13 @@ Private Packagist Self-Hosted requires PostgreSQL, Redis, and blob storage to st
26
26
You can either use the built-in options that come with the Helm chart or use your own PostgreSQL, Redis, and blob storage.
27
27
For blob storage, we currently support Azure Blob Storage, Google Cloud Storage, AWS S3, and other S3-compatible storage solutions.
28
28
29
-
Please note that if you chose to use the built-int solution then each of the storage requires one or more volumes using
29
+
Please note that if you choose to use the built-in solution then each of the storage requires one or more volumes using
30
30
[dynamic volume provision](https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/) to allocate storage for the different Pods.
31
-
Configure the Storage Class in global values section.
31
+
Configure the Storage Class in the values.yaml under `global.storageClass`.
32
32
33
33
### Annotated configuration
34
34
35
-
To install the Private Packagist Self-Hosted Helm Chart configure values based on your setup, store them in a YAML file, e.g. values.yaml, and then run the commands below.
35
+
To install the Private Packagist Self-Hosted Helm Chart configure values based on your setup, store them in a YAML file, e.g. `values.yaml`, and then run the commands below.
36
36
37
37
HELM_CHART_VALUES_FILE
38
38
@@ -91,7 +91,7 @@ You can configure the blog storage in the values.yaml under `storage.type`.
91
91
The Private Packagist Self-Hosted application expects that TLS termination happens at or before the Ingress level.
92
92
All traffic within the cluster is unencrypted.
93
93
94
-
Make sure your Kubernetes network plugin encrypts connections between pods to avoid potential security issues.
94
+
Ensure your Kubernetes network plugin encrypts connections between pods to avoid potential security issues.
0 commit comments