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
Copy file name to clipboardExpand all lines: README.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,11 +107,13 @@ Following table lists all the parameters supported by the latest MarkLogic Helm
107
107
|`updateStrategy.type`| Update strategy for MarkLogic pods |`OnDelete`|
108
108
|`terminationGracePeriod`| Seconds the MarkLogic Pod terminate gracefully |`120`|
109
109
|`clusterDomain`| Domain for the Kubernetes cluster |`cluster.local`|
110
+
|`allowLongHostnames`| Allow deployment with hostname over 64 characters |`false`|
111
+
|`useLegacyHostnames`| Use the lagecy hostnames that is used before 1.1.0 version. |`false`|
110
112
|`group.name`| Group name for joining MarkLogic cluster |`Default`|
111
113
|`group.enableXdqpSsl`| SSL encryption for XDQP |`true`|
112
114
|`bootstrapHostName`| Host name of MarkLogic bootstrap host (to join a cluster) |`""`|
113
115
|`image.repository`| Repository for MarkLogic image |`marklogicdb/marklogic-db`|
114
-
|`image.tag`| Image tag for MarkLogic image |`11.1.0-centos-1.1.2`|
116
+
|`image.tag`| Image tag for MarkLogic image |`11.2.0-centos-1.1.2`|
115
117
|`image.pullPolicy`| Image pull policy for MarkLogic image |`IfNotPresent`|
116
118
|`initContainers.configureGroup.image`| Image for configureGroup InitContainer |`curlimages/curl:8.6.0`|
117
119
|`initContainers.configureGroup.pullPolicy`| Pull policy for configureGroup InitContainer |`IfNotPresent`|
@@ -226,7 +228,8 @@ Following table lists all the parameters supported by the latest MarkLogic Helm
226
228
2. The MarkLogic Docker image must be run in privileged mode. At the moment if the image isn't run as privileged many calls that use sudo during the startup script will fail due to lack of required permissions as the image will not be able to create a user with the required permissions.
227
229
3. The latest released version of CentOS 7 has known security vulnerabilities with respect to glib2 CVE-2016-3191, CVE-2015-8385, CVE-2015-8387, CVE-2015-8390, CVE-2015-8394, CVE-2016-3191, glibc CVE-2019-1010022, pcre CVE-2015-8380, CVE-2015-8387, CVE-2015-8390, CVE-2015-8393, CVE-2015-8394, SQLite CVE-2019-5827. These libraries are included in the CentOS base image but, to-date, no fixes have been made available. Even though these libraries may be present in the base image that is used by MarkLogic Server, they are not used by MarkLogic Server itself, hence there is no impact or mitigation required.
228
230
4. The latest released version of fluent/fluent-bit:2.2.2 has known security vulnerabilities with respect to libcom-err2 CVE-2022-1304, libgcrypt20 CVE-2021-33560, libgnutls30 CVE-2024-0567, libldap-2.4-2 CVE-2023-2953, libzstd1 CVE-2022-4899, zlib1g CVE-2023-45853. These libraries are included in the Debian base image but, to-date, no fixes have been made available. For libpq5 CVE-2024-0985, we wait for a future upgrade of the fluent-bit image to include the fix. We will provide updates and mitigation strategies as soon as more information becomes available.
229
-
5. The latest released version of redhat/ubi9:9.3 has known security vulnerabilities with respect to setuptools GHSA-r9hx-vwmv-q579, we wait for a future upgrade of the redhad ubi image to include the fix.
231
+
5. The latest released version of redhat/ubi9:9.3 has known security vulnerabilities with respect to setuptools GHSA-r9hx-vwmv-q579. We wait for a future upgrade of the redhad ubi image to include the fix.
230
232
6. The security context “allowPrivilegeEscalation” is set to TRUE by default in values.yaml file and cannot be changed to run the current MarkLogic container. Work is in progress to run MarkLogic container in "rootless" mode.
231
-
7. The Readiness and Startup Probe are not compatible with HA deployment. At the moment these probes may fail in the case of Security database failover. As of the 1.0.2 helm chart release, the startup and readiness probes are disabled by default.
232
-
8. Path based routing and Ingress features are only supported with MarkLogic 11.1 and higher.
233
+
7. 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
234
+
8. The Readiness and Startup Probe are not compatible with HA deployment. At the moment these probes may fail in the case of Security database failover. As of the 1.0.2 helm chart release, the startup and readiness probes are disabled by default.
235
+
9. Path based routing and Ingress features are only supported with MarkLogic 11.1 and higher.
{{- $chartVersionDigit := int $chartVersionString}}
62
+
{{- iflt$chartVersionDigit 110 -}}
63
+
{{- $errorMessage := printf "A new algorithm for generating hostnames was introduced in version 1.1.0. When upgrading from version %s to version %s, the \"useLegacyHostnames\" setting must be set to true to prevent the StatefulSet from being recreated. Please add the following to the values file and attempt the upgrade again: \n\nuseLegacyHostnames: true\n"$chartVersionWithDot .Chart.Version }}
64
+
{{- fail $errorMessage}}
65
+
{{- end }}
66
+
{{- end }}
67
+
{{- end }}
68
+
{{- end }}
69
+
{{- end }}
70
+
71
+
{{/*
72
+
{{- end }}
73
+
{{- end }}
74
+
8
75
{{/*
9
76
Create a default fully qualified app name.
10
77
We truncate at 63 chars because some Kubernetes name fields are limited to this (by the DNS naming spec).
11
-
The release name will be used as full name
78
+
To surrport the upgrade from 1.0.x to 1.1.x, we keep the old name when doing upgrade from 1.0.x.
79
+
For the new install, we use the new name, which is the release name.
{{- $errorMessage := printf "%s%s%s""The FQDN: "$fqdn" is longer than 64. Please use a shorter release name and try again. MarkLogic App Server does not support turning on SSL with FQDN over 64 characters. If you still want to install with an FQDN longer than 64 characters, you can override this restriction by setting allowLongHostnames: true in your Helm values file."}}
0 commit comments