Skip to content

Commit 5f7f0ca

Browse files
MLE-15630: readme changes suggested by PM (#278)
* readme changes * Update README.md
1 parent 44672c9 commit 5f7f0ca

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

README.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -234,8 +234,9 @@ Following table lists all the parameters supported by the latest MarkLogic Helm
234234

235235
## Known Issues and Limitations
236236

237-
1. If the hostname is greater than 64 characters there will be issues with certificates. It is highly recommended to use hostname shorter than 64 characters or use SANs for hostnames in the certificates. If you still choose to use hostname greater than 64 characters, set "allowLongHostnames" to True.
237+
1. If the hostname is greater than 64 characters there will be issues with certificates. It is highly recommended to use hostname shorter than 64 characters or use SANs for hostnames in the certificates. If you still choose to use hostname greater than 64 characters, set "allowLongHostnames" to true.
238238
2. The latest released version of fluent/fluent-bit:3.1.1 has known high and critical 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.
239-
3. The security context “allowPrivilegeEscalation” is set to False by default in values.yaml file and should not be changed to run the MarkLogic container with default rootless image. If you choose to use image with root privileges, set "allowPrivilegeEscalation" to True.
239+
3. The security context “allowPrivilegeEscalation” is set to false by default in the
240+
values.yaml file. This should not be changed when running the MarkLogic container with default rootless image. If you choose to use an image with root privileges, set "allowPrivilegeEscalation" to true.
240241
4. 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.
241-
5. Path based routing and Ingress features are only supported with MarkLogic 11.1 and higher.
242+
5. Path-based routing and Ingress features are only supported with MarkLogic 11.1 and higher.

0 commit comments

Comments
 (0)