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-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -154,18 +154,18 @@ Following table lists all the parameters supported by the latest MarkLogic Helm
154
154
|`containerSecurityContext.runAsNonRoot`| Indicates that the container must run as a non-root user |`true`|
155
155
|`containerSecurityContext.allowPrivilegeEscalation`| Controls whether a process can gain more privileges than its parent process |`true`|
156
156
|`livenessProbe.enabled`| Parameter to enable the liveness probe |`true`|
157
-
|`livenessProbe.initialDelaySeconds`| Initial delay seconds for liveness probe |`30`|
158
-
|`livenessProbe.periodSeconds`| Period seconds for liveness probe |`60`|
157
+
|`livenessProbe.initialDelaySeconds`| Initial delay seconds for liveness probe |`300`|
158
+
|`livenessProbe.periodSeconds`| Period seconds for liveness probe |`20`|
159
159
|`livenessProbe.timeoutSeconds`| Timeout seconds for liveness probe |`5`|
160
-
|`livenessProbe.failureThreshold`| Failure threshold for liveness probe |`3`|
160
+
|`livenessProbe.failureThreshold`| Failure threshold for liveness probe |`15`|
161
161
|`livenessProbe.successThreshold`| Success threshold for liveness probe |`1`|
162
-
|`readinessProbe.enabled`| Use this parameter to enable the readiness probe|`true`|
162
+
|`readinessProbe.enabled`| Use this parameter to enable the readiness probe. See [Known-Issues-and-Limitations](#known-issues-and-limitations) section|`true`|
163
163
|`readinessProbe.initialDelaySeconds`| Initial delay seconds for readiness probe |`10`|
164
164
|`readinessProbe.periodSeconds`| Period seconds for readiness probe |`60`|
165
165
|`readinessProbe.timeoutSeconds`| Timeout seconds for readiness probe |`5`|
166
166
|`readinessProbe.failureThreshold`| Failure threshold for readiness probe |`3`|
167
167
|`readinessProbe.successThreshold`| Success threshold for readiness probe |`1`|
168
-
|`startupProbe.enabled`| Parameter to enable startup probe|`true`|
168
+
|`startupProbe.enabled`| Parameter to enable startup probe. See [Known-Issues-and-Limitations](#known-issues-and-limitations) section|`true`|
169
169
|`startupProbe.initialDelaySeconds`| Initial delay seconds for startup probe |`10`|
170
170
|`startupProbe.periodSeconds`| Period seconds for startup probe |`20`|
171
171
|`startupProbe.timeoutSeconds`| Timeout seconds for startup probe |`1`|
@@ -210,4 +210,5 @@ Following table lists all the parameters supported by the latest MarkLogic Helm
210
210
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.
211
211
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.
212
212
4. TLS cannot be turned on at the MarkLogic level for the Admin (port 8001) and Manage (port 8002) app servers. TLS can be configured for any/all other ports at the MarkLogic level and if the Admin and Manage ports need to be exposed outside of the Kubernetes network, TLS can be terminated at the load balancer. Alternatively, additional custom app servers can be configured to serve the Admin UI and Management REST API on custom ports with TLS configured.
213
-
5. With respect to security context “allowPrivilegeEscalation” is set to TRUE by default in values.yaml file to run MarkLogic container. Work is in progress to run MarkLogic container as rootless user.
213
+
5. With respect to security context “allowPrivilegeEscalation” is set to TRUE by default in values.yaml file to run MarkLogic container. Work is in progress to run MarkLogic container as rootless user.
214
+
6. 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.
0 commit comments