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
- If you are running on Mac OSX, you will need Virtual Box: [Virtual Box](https://www.virtualbox.org/)
36
-
- Virtual Box is used as the VM for the Minikube Kubernetes environment which will host the MarkLogic Server Application
36
+
- Virtual Box is used as the VM for the Minikube Kubernetes environment, which will host the MarkLogic Server Application.
37
37
- The latest version of a supported web browser. See the list here: [Web Browser](https://developer.marklogic.com/products/support-matrix/)
38
38
39
39
@@ -42,12 +42,15 @@ This section describes the procedure for setting up Minikube, installing MarkLog
42
42
43
43
44
44
## Setting Up Minikube
45
-
First we need to setup the Kubernetes control plane on our local machine, Minikube is an easy tool which handles setting up a Kubernetes enviornment locally.
45
+
First you will need to set up the Kubernetes control plan on your local machine. Minikube is a tool that makes it easy to set up a local Kubernetes enviornment.
- If you are running in a Linux OS: `minikube start --driver=docker`
49
-
To verify the minikube started correctly we can use the Kubernetes command line tool, KubeCTL:
50
-
```sh
47
+
- Start Minikube:
48
+
`minikube start --driver=virtualbox`
49
+
- If you are running in a Linux OS: `minikube start --driver=docker`
50
+
51
+
To verify the Minikube started correctly, use the Kubernetes command line tool, KubeCTL:
52
+
53
+
``sh
51
54
kubectl get nodes
52
55
```
53
56
```
@@ -56,10 +59,13 @@ NAME STATUS ROLES AGE VERSION
56
59
minikube Ready control-plane,master 1d v1.23.3
57
60
```
58
61
59
-
- Enable Addons: `minikube addons enable ingress` for ingress.
60
-
## Installing a Single MarkLogic Host to minikube
61
-
- Push the image used for MarkLogic Server to the VM: `minikube image load store/marklogicdb/marklogic-server:10.0-9-centos-1.0.0-ea4`
62
-
- The above Image ID: `store/marklogicdb/marklogic-server:10.0-9-centos-1.0.0-ea4` is whatever the latest image is, to find the latest id go to https://hub.docker.com/_/marklogic
62
+
- Enable Addons:
63
+
`minikube addons enable ingress`
64
+
for ingress.
65
+
## Installing a Single MarkLogic Host to Minikube
66
+
- Push the image used for MarkLogic Server to the VM:
- For the image ID in this example,`store/marklogicdb/marklogic-server:10.0-9-centos-1.0.0-ea4` is what the latest image is. To find the latest id go to https://hub.docker.com/_/marklogic
63
69
- Navigate to where you downloaded or cloned the MarkLogic Helm repository.
64
70
- Verify that the image loaded to Minikube with the comand above matches the `repository` and `tag` in the `values.yaml`.
- Navigate to the `/charts` folder in your local directory.
71
-
- Run `helm install RELEASE_NAME .` where the `RELEASE_NAME` can be any name you want to use to identify this deployment. For example: `helm install marklogic-local-dev-env .`.
77
+
- Run `helm install RELEASE_NAME .` where the `RELEASE_NAME` can be any name you want to use to identify this deployment.
78
+
For example: `helm install marklogic-local-dev-env .`.
72
79
## Installing Multiple MarkLogic Hosts to Minikube
73
80
TODO
74
81
@@ -87,7 +94,7 @@ This process may take a minute or two.
87
94
```sh
88
95
kubectl port-forward marklogic-0 8001 8000 7997
89
96
```
90
-
If you want to forward other ports just append them to the command separated by a space
97
+
If you want to forward other ports, just append them to the command separated by a space.
- To complete this step, access your browser and navigate to `localhost:8001`. You should see the MarkLogic Server Admin interface.
99
-
If you are unable to see the MarkLogic Server Admin Interface, see the Debugging section to gather more information about the cluster and potential errors.
106
+
If you are unable to see the MarkLogic Server Admin interface, see the [Debugging](#Debugging) section to gather more information about the cluster and potential errors.
100
107
101
-
- When you are finished, see the [Cleanup](##Cleanup) section in order to teardown the cluster when finished
108
+
- When you are done, see the [Cleanup](##Cleanup) section in order to teardown the cluster when done.
102
109
103
110
# Debugging
104
111
This Debugging section contains useful commands to help debug a Kubernetes cluster running MarkLogic Server. Additional information and commands can be found here: https://kubernetes.io/docs/tasks/debug-application-cluster/debug-running-pod/
@@ -109,7 +116,7 @@ This command provides additional information about the state of each pod in the
109
116
kubectl describe pods
110
117
```
111
118
The command outputs a large amount of data and contains a lot of information. Pay attention to the events section near the bottom of the output to view the state of events, and what occurred during the startup of the pod.
112
-
EX:
119
+
For Example:
113
120
114
121
```
115
122
...
@@ -126,13 +133,13 @@ Events:
126
133
127
134
-----
128
135
129
-
Run the following command to see the logs on a specific pod:
136
+
Run the following command to see the logs for a specific pod:
130
137
```sh
131
138
kubectl logs {POD_NAME}
132
139
```
133
140
The `{POD_NAME}` can be found with the `kubectl get pods` command.
0 commit comments