|
1 | 1 | # MarkLogic Kubernetes Helm Chart
|
2 | 2 |
|
3 |
| -- [MarkLogic Kubernetes Helm Chart](#marklogic-kubernetes-helm-chart) |
4 | 3 | - [Introduction](#introduction)
|
5 | 4 | - [Prerequisites](#prerequisites)
|
6 | 5 | - [Set up the required tools](#set-up-the-required-tools)
|
|
12 | 11 | - [Install eksctl](#install-eksctl)
|
13 | 12 | - [Using eksctl to provision Kubernetes cluster on EKS](#using-eksctl-to-provision-kubernetes-cluster-on-eks)
|
14 | 13 | - [Suggestions for Naming](#suggestions-for-naming)
|
15 |
| -- [Install Marklogic Helm Chart](#install-marklogic-helm-chart) |
16 |
| - - [Add Marklogic Repo](#add-marklogic-repo) |
| 14 | +- [Install MarkLogic Helm Chart](#install-marklogic-helm-chart) |
| 15 | + - [Add MarkLogic Repo](#add-marklogic-repo) |
17 | 16 | - [Installing the Chart](#installing-the-chart)
|
18 | 17 | - [Configuration Options](#configuration-options)
|
19 | 18 | - [--values](#--values)
|
|
31 | 30 |
|
32 | 31 | # Introduction
|
33 | 32 |
|
34 |
| -MarkLogic Server is a multi-model database that has both NoSQL and trusted enterprise data management capabilities. It is the most secure multi-model database. |
35 |
| - |
36 |
| -This custom Helm Chart deploys MarkLogic Server on Kubernetes using Helm. |
| 33 | +This tutorial describes how to set up Kubernetes development environment with AWS EKS and MarkLogic Server. It covers these tasks: |
| 34 | +- Set up the prerequisites necessary for setting up MarkLogic Server in Kubernetes |
| 35 | +- How to setup Kubernetes cluster and install MarkLogic Server on Minikube |
| 36 | +- How to setup Kubernetes cluster and install MarkLogic Server on AWS EKS using eksctl |
| 37 | +- Access the MarkLogic Server cluster |
| 38 | +- How to clean up your environment |
| 39 | +- List of parameters used for configuration |
37 | 40 |
|
38 | 41 | # Prerequisites
|
39 | 42 |
|
@@ -106,11 +109,11 @@ eksctl create cluster \
|
106 | 109 | * KUBERNETES_VERSION: For now, we only support the latest version of Kubernetes in EKS, which is 1.21.
|
107 | 110 | * NODEGROUP_NAME: Choose a distinctive node group name.
|
108 | 111 | * NODE_TYPE: The recommendation from our performance team is to use the r5.large node type for development purposes.
|
109 |
| -* NUMBER_OF_NODES: Total number of nodes running not only Marklogic database, but also nodes running other applications. |
| 112 | +* NUMBER_OF_NODES: Total number of nodes running not only MarkLogic database, but also nodes running other applications. |
110 | 113 |
|
111 |
| -# Install Marklogic Helm Chart |
| 114 | +# Install MarkLogic Helm Chart |
112 | 115 |
|
113 |
| -## Add Marklogic Repo |
| 116 | +## Add MarkLogic Repo |
114 | 117 |
|
115 | 118 | If you haven’t already, add the MarkLogic official repo to Helm using this command:
|
116 | 119 |
|
@@ -297,7 +300,7 @@ To use transactional functionality with MarkLogic, you have to set up Ingress an
|
297 | 300 | Use this Helm command to uninstall the chart:
|
298 | 301 |
|
299 | 302 | ```
|
300 |
| -helm delete my-release |
| 303 | +helm uninstall my-release |
301 | 304 | ```
|
302 | 305 |
|
303 | 306 | The output will look like this:
|
@@ -329,6 +332,7 @@ This table describes the list of available parameters for Helm Chart.
|
329 | 332 | | `resources.limits` | The resource limits for MarkLogic container | `{}` |
|
330 | 333 | | `resources.requests` | The resource requests for MarkLogic container | `{}` |
|
331 | 334 | | `nameOverride` | String to override the app name | `""` |
|
| 335 | +| `fullnameOverride` | String to completely replace the generated name | `""` | |
332 | 336 | | `auth.adminUsername` | Username for default MarkLogic Administrator | `admin` |
|
333 | 337 | | `auth.adminPassword` | Password for default MarkLogic Administrator | `admin` |
|
334 | 338 | | `affinity` | Affinity property for pod assignment | `{}` |
|
|
0 commit comments