|
| 1 | +## 3-Node Artifactory Cluster with Distribution and direct-S3 Provider |
| 2 | + |
| 3 | +### Overall |
| 4 | +| Product | Enabled | |
| 5 | +|-------------|-------------| |
| 6 | +| Artifactory | ✅ | |
| 7 | +| xray | ❌ | |
| 8 | +| distribution | ✅ | |
| 9 | +| insight | ❌ | |
| 10 | +| pipelines | ❌ | |
| 11 | +| worker | ❌ | |
| 12 | + |
| 13 | + |
| 14 | +### Artifactory |
| 15 | +| Detail | Value | |
| 16 | +|-------------|-------------| |
| 17 | +| Replica | 3 | |
| 18 | +| Database | External Postgres | |
| 19 | +| Persistence | Default Storage Class + S3 | |
| 20 | +| SSL | ✅ | |
| 21 | +| Ingress | ❌ | |
| 22 | +| Nginx Deployment | ✅ | |
| 23 | +| UnifiedSecret | ✅ | |
| 24 | +| Non-Default Admin Credential | ✅ | |
| 25 | +| Default Master Key | ❌ | |
| 26 | +| Sizing Parameters | artifactory-xlarge | |
| 27 | +| Private Registry | ✅ | |
| 28 | + |
| 29 | + |
| 30 | +### Distribution |
| 31 | + |
| 32 | +| Detail | Value | |
| 33 | +|-------------|-------------| |
| 34 | +| Replica | 2 | |
| 35 | +| Database | External Postgres | |
| 36 | +| Persistence | Default Storage Class | |
| 37 | +| External Redis | ❌ | |
| 38 | +| SSL | ✅ | |
| 39 | +| UnifiedSecret | ❌ | |
| 40 | +| Sizing Parameters | distribution-xlarge | |
| 41 | +| Private Registry | ✅ | |
| 42 | + |
| 43 | +## Install |
| 44 | + |
| 45 | +1. In `values-main.yaml`, add your Artifactory hostname as `jfrogUrl`. |
| 46 | + |
| 47 | +2. To pull images from a private registry, create your own `imagePullSecrets` and fill in `imagePullSecrets` and `imageRegistry` in `values-main.yaml`: |
| 48 | + |
| 49 | + ``` |
| 50 | + $ kubectl create secret docker-registry regsecret --docker-server=<your-registry-server> --docker-username=<your-name> --docker-password=<your-pword> --docker-email=<your-email> |
| 51 | + ``` |
| 52 | + |
| 53 | +3. Passing secret: |
| 54 | + |
| 55 | + If you want to change the secret name, remember to update the reference in `values-main.yaml` or `values-artifactory.yaml` |
| 56 | + |
| 57 | + a. Master Key |
| 58 | + |
| 59 | + ``` |
| 60 | + $ kubectl create secret generic my-master-key --from-literal=master-key="$(openssl rand -hex 32)" -n <namespace> |
| 61 | + ``` |
| 62 | + |
| 63 | + b. Join Key |
| 64 | + |
| 65 | + ``` |
| 66 | + $ kubectl create secret generic my-join-key --from-literal=join-key="$(openssl rand -hex 32)" -n <namespace> |
| 67 | + ``` |
| 68 | + |
| 69 | + c. CA Certificate for SSL |
| 70 | + |
| 71 | + Passing your own `ca.crt` for artifactory if needed for ssl configuration. See prerequisite for `ca.crt`. [here](https://jfrog.com/help/r/jfrog-installation-setup-documentation/prerequisites-for-custom-tls-certificate) |
| 72 | + |
| 73 | + ``` |
| 74 | + $ kubectl create secret tls my-cacert --cert=ca.crt --key=ca.private.key -n <namespace> |
| 75 | + ``` |
| 76 | + |
| 77 | + d. Default Admin Credentials |
| 78 | + |
| 79 | + ``` |
| 80 | + $ kubectl create secret generic my-admin --from-literal=bootstrap.creds="$(printf "%s@%s=%s" admin 127.0.0.1 password| base64 )" -n <namespace> |
| 81 | + ``` |
| 82 | + |
| 83 | +4. Fill in database details ( `values-artifactory.yaml` ). [See here for more details related to database.](https://jfrog.com/help/r/jfrog-installation-setup-documentation/database-configuration) |
| 84 | + |
| 85 | + ``` |
| 86 | + $ kubectl create secret generic my-database --from-literal=db-url='database_url' --from-literal=db-user='admin_user' --from-literal=db-password='password' -n <namespace> |
| 87 | + $ kubectl create secret generic my-distribution-database --from-literal=db-url='database_url' --from-literal=db-user='admin_user' --from-literal=db-password='password' -n <namespace> |
| 88 | + ``` |
| 89 | + |
| 90 | +5. Create the `binarystore.xml` secret or pull the values from environment variables. |
| 91 | + |
| 92 | + ``` |
| 93 | + $ kubectl create secret generic my-binarystore --from-file=binarystore.xml |
| 94 | + ``` |
| 95 | + |
| 96 | + [Create an IAM role with `AmazonS3FullAccess` permission](https://jfrog.com/help/r/active/artifactory-connect-artifactory-to-s3-bucket-with-iam-role) |
| 97 | + |
| 98 | + Associate an IAM role to the service account in `values-artifactory.yaml` by specifying the ARN: |
| 99 | + |
| 100 | + ``` |
| 101 | + serviceAccount: |
| 102 | + create: true |
| 103 | + annotations: |
| 104 | + eks.amazonaws.com/role-arn: arn:aws:iam::<ACCOUNT_ID>:role/<IAM_ROLE_NAME> |
| 105 | + ``` |
| 106 | + |
| 107 | +6. Pull charts ( if you need to reference the suggested sizing paramerters ) and install |
| 108 | + |
| 109 | + In this example, we are going to reference the baseline xlarge sizing parameters for our Artifactory and Distribution release. To do so, first pull and untar the chart. You may skip these steps and add/create your own sizing parameter YAML. |
| 110 | + |
| 111 | + See more details regarding the baseline sizing parameters [here](https://jfrog.com/help/r/jfrog-platform-reference-architecture/jfrog-platform-reference-architecture) |
| 112 | + |
| 113 | + ``` |
| 114 | + $ helm repo update |
| 115 | + $ helm pull jfrog/jfrog-platform --untar |
| 116 | + ``` |
| 117 | + |
| 118 | + ``` |
| 119 | + $ helm install <name> jfrog/jfrog-platform -n <namespace> -f values-main.yaml -f values-artifactory.yaml -f values-distribution.yaml -f jfrog-platform/charts/artifactory/sizing/artifactory-xlarge.yaml -f jfrog-platform/charts/distribution/sizing/distribution-xlarge.yaml |
| 120 | + ``` |
| 121 | + |
| 122 | +7. If installing on OpenShift, add values-openshift.yaml: |
| 123 | + |
| 124 | + ``` |
| 125 | + $ helm install <name> jfrog/jfrog-platform -n <namespace> -f values-main.yaml -f values-artifactory.yaml -f values-distribution.yaml -f values-openshift.yaml -f jfrog-platform/charts/artifactory/sizing/artifactory-xlarge.yaml -f jfrog-platform/charts/distribution/sizing/distribution-xlarge.yaml |
| 126 | + ``` |
| 127 | + |
| 128 | +Note: To install on OpenShift out-of-the-box, you need Distribution chart 102.23.0+, so the minimum platform chart version is 10.17.4+. |
0 commit comments