|
1 | 1 | # MarkLogic Kubernetes Helm Chart
|
2 | 2 |
|
| 3 | +- [MarkLogic Kubernetes Helm Chart](#marklogic-kubernetes-helm-chart) |
3 | 4 | - [Introduction](#introduction)
|
4 | 5 | - [Prerequisites](#prerequisites)
|
5 | 6 | - [Set Up the Required Tools](#set-up-the-required-tools)
|
|
17 | 18 | - [Configuration Options](#configuration-options)
|
18 | 19 | - [--values](#--values)
|
19 | 20 | - [--set](#--set)
|
| 21 | + - [Setting MarkLogic admin password](#setting-marklogic-admin-password) |
| 22 | + - [Log Collection](#log-collection) |
| 23 | + - [Adding and Removing Hosts from Clusters](#adding-and-removing-hosts-from-clusters) |
| 24 | + - [Adding Hosts](#adding-hosts) |
| 25 | + - [Removing Hosts](#removing-hosts) |
20 | 26 | - [Access the MarkLogic Server](#access-the-marklogic-server)
|
21 | 27 | - [Service](#service)
|
22 | 28 | - [Get the ClusterIP Service Name](#get-the-clusterip-service-name)
|
@@ -223,42 +229,20 @@ We recommend that you use the `values.yaml` file for configuring your installati
|
223 | 229 |
|
224 | 230 | ## Setting MarkLogic admin password
|
225 | 231 |
|
226 |
| -By default, a randomly generated aphanumeric value will be set for MarkLogic admin password. This value is stored in Kuberenetes secrets. |
227 |
| -User can also set a custom password by setting a value for adminPassword in the values.yaml file or using the `--set` flag. |
| 232 | +If the password does not provided when installing the MarkLogic Chart, a randomly generated aphanumeric value will be set for MarkLogic admin password. This value is stored in Kuberenetes secrets. |
| 233 | +User can also set a custom password by setting auth.adminPassword value during installation. |
228 | 234 | To retrieve the randomly generated admin password, use the following commands:
|
229 | 235 |
|
230 |
| -1. List the secrets for helm deployment: |
| 236 | +1. List the secrets for MarkLogic deployment: |
231 | 237 | ```
|
232 | 238 | kubectl get secrets
|
233 | 239 | ```
|
234 |
| -The output will be similar to: |
| 240 | +Identify the name of the secret. |
235 | 241 |
|
236 |
| -| NAME | TYPE | DATA | AGE | |
237 |
| -| :--- | :---: | ---: | ---: | |
238 |
| -| dnode-group-marklogic | kubernetes.io/basic-auth | 2 | 33s | |
239 |
| - |
240 |
| -2. Get the encoded value for admin password: |
241 |
| -``` |
242 |
| -kubectl get secret dnode-group-marklogic -o jsonpath='{.data}' |
243 |
| -``` |
244 |
| -The output will be similar to: |
245 |
| -``` |
246 |
| -{"password":"R0JYaWxzR2c=","username":"YWRtaW4="} |
247 |
| -``` |
248 |
| -3. Decode the password secret: |
249 |
| -``` |
250 |
| -echo 'R0JYaWxzR2c=' | base64 --decode |
| 242 | +2. Save the secret name from step 1 to get the admin password using the following script : |
251 | 243 | ```
|
252 |
| -The output will be similar to: |
| 244 | +kubectl get secret SECRET_NAME -o jsonpath='{.data}' |
253 | 245 | ```
|
254 |
| -GBXilsGg |
255 |
| -``` |
256 |
| - |
257 |
| -To upgrade the helm charts or deploy new helm charts for multi-node cluster, use the encoded value for admin password from the output of step 2. |
258 |
| - |
259 |
| -To access the MarkLogic cluster use the decode value for admin password from the output of step 3. |
260 |
| - |
261 |
| - |
262 | 246 | ### Log Collection
|
263 | 247 |
|
264 | 248 | To enable log collection for all Marklogic logs set logCollection.enabled to true. Set each option in logCollection.files to true of false depending on if you want to track each type of Marklogic log file.
|
|
0 commit comments