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
string(name: 'E2E_MARKLOGIC_IMAGE_VERSION', defaultValue: 'ml-docker-db-dev-tierpoint.bed-artifactory.bedford.progress.com/marklogic/marklogic-server-ubi-rootless:latest-12', description: 'Docker image to use for tests.', trim: true)
217
-
string(name: 'VERSION', defaultValue: '1.1.0', description: 'Version to tag the image with.', trim: true)
230
+
string(name: 'VERSION', defaultValue: '1.2.0', description: 'Version to tag the image with.', trim: true)
218
231
booleanParam(name: 'PUBLISH_IMAGE', defaultValue: false, description: 'Publish image to internal registry')
219
232
string(name: 'emailList', defaultValue: emailList, description: 'List of email for build notification', trim: true)
3. Make sure the Marklogic Operator pod is running:
35
+
3. Make sure the MarkLogic Operator pod is running:
36
36
```sh
37
37
kubectl get pods -n marklogic-operator-system
38
38
```
39
39
40
40
4. Use this command to verify CRDs are correctly installed:
41
41
```sh
42
-
kubectl get crd -n marklogic-operator-system | grep 'marklogic'
42
+
kubectl get crd -n marklogic-operator-system | grep 'marklogic'
43
43
```
44
44
45
45
### Install MarkLogic Cluster
46
-
Once MarkLogic Operator Pod is running, use your custom manifests or choose from sample manifests from this repository located in the ./config/samples directory.
47
-
Optionally, create a dedicated namespace for new MarkLogic resources.
48
-
```sh
49
-
kubectl create namespace <namespace-name>
50
-
```
51
-
To deploy marklogic single group, use the `quick_start.yaml` from the config/samples:
Once the installation is complete and the pod is in a running state, the MarkLogic Admin UI can be accessed using the port-forwarding command:
46
+
Once MarkLogic Operator Pod is running, use your custom manifests or choose from sample manifests from this repository located in the `./config/samples` directory.
47
+
Optionally, create a dedicated namespace for new MarkLogic resources:
48
+
```sh
49
+
kubectl create namespace <namespace-name>
50
+
```
51
+
52
+
To deploy a MarkLogic single group, use the `quick_start.yaml` from the `config/samples`:
If you used the automatically generated admin credentials, use these steps to extract the admin username, password, and wallet-password from a secret:
62
63
63
64
1. Run this command to fetch all of the secret names:
64
-
```sh
65
-
kubectl get secrets --namespace=<namespace-name>
66
-
```
67
-
The MarkLogic admin secret name is in the format `<marklogicCluster-name>-admin`. For example if markLogicCluster name is `single-node`, the secret name is `single-node-admin`.
65
+
```sh
66
+
kubectl get secrets --namespace=<namespace-name>
67
+
```
68
+
The MarkLogic admin secret name is in the format `<marklogicCluster-name>-admin`. For example, if the markLogicCluster name is `single-node`, the secret name is `single-node-admin`.
68
69
69
70
2. Using the secret name from step 1, retrieve the MarkLogic admin credentials using these commands:
70
-
```sh
71
-
kubectl get secret single-node-admin --namespace=<namespace-name> -o jsonpath='{.data.username}'| base64 --decode;echo
71
+
```sh
72
+
kubectl get secret single-node-admin --namespace=<namespace-name> -o jsonpath='{.data.username}'| base64 --decode;echo
72
73
73
-
kubectl get secret single-node-admin --namespace=<namespace-name> -o jsonpath='{.data.password}'| base64 --decode;echo
74
+
kubectl get secret single-node-admin --namespace=<namespace-name> -o jsonpath='{.data.password}'| base64 --decode;echo
74
75
75
-
kubectl get secret single-node-admin --namespace=<namespace-name> -o jsonpath='{.data.wallet-password}'| base64 --decode;echo
76
-
```
76
+
kubectl get secret single-node-admin --namespace=<namespace-name> -o jsonpath='{.data.wallet-password}'| base64 --decode;echo
77
+
```
77
78
78
79
For additional manifests to deploy a MarkLogic cluster inside a Kubernetes cluster, see [Operator manifest](https://docs.progress.com/bundle/marklogic-server-on-kubernetes/operator/Operator-manifest.html) in the documentation.
79
80
80
81
## Clean Up
81
82
82
83
#### Cleaning up MarkLogic Cluster
83
-
Use this step to delete MarkLogic cluster and other resources created from the manifests used in the above [step](#install-marklogic-cluster):
> **Note for version 1.2.0 and later:** The MarkLogic Operator includes the `helm.sh/resource-policy: keep` annotation. When you delete the operator using the Helm command above, the Custom Resource Definitions (CRDs) and your existing MarkLogic deployments are preserved and will **not** be deleted automatically.
102
+
103
+
#### Deleting Custom Resource Definitions (CRDs)
104
+
To perform a complete system wipe and manually delete the Custom Resource Definitions (CRDs):
105
+
106
+
**Warning:** Deleting a CRD will automatically delete all Custom Resources of that type across the entire Kubernetes cluster. Only proceed if you are certain you want to permanently remove all MarkLogic resources.
1. The latest released version of fluent/fluent-bit:4.1.1 has high security vulnerabilities. If you decide to enable the log collection feature, choose and deploy the fluent-bit or an alternate image with no vulnerabilities as per your requirements.
98
-
2. Known Issues and Limitations for the MarkLogic Server Docker image can be viewed using the link: https://github.com/marklogic/marklogic-docker?tab=readme-ov-file#Known-Issues-and-Limitations.
99
-
3. If you're updating the group name configuration, ensure that you delete the pod to apply the changes, as we are using the OnDelete upgrade strategy.
115
+
1. The latest released version of `fluent/fluent-bit:4.1.1` has high security vulnerabilities. If you decide to enable the log collection feature, choose and deploy the fluent-bit or an alternate image with no vulnerabilities as per your requirements.
116
+
2. Known Issues and Limitations for the MarkLogic Server Docker image can be viewed using the link: [https://github.com/marklogic/marklogic-docker?tab=readme-ov-file#Known-Issues-and-Limitations](https://github.com/marklogic/marklogic-docker?tab=readme-ov-file#Known-Issues-and-Limitations).
117
+
3. If you're updating the group name configuration, ensure that you delete the pod to apply the changes, as we are using the OnDelete upgrade strategy.
0 commit comments