Skip to main content

MarkLogic Server on Kubernetes

Known issues and limitations

  1. If the hostname is greater than 64 characters there will be issues with certificates. It is highly recommended to use a 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.

  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.

  3. The security context allowPrivilegeEscalation is set to false by default in the values.yaml file. This should not be changed when running the MarkLogic container with the default rootless image. If you choose to use an image with root privileges, set allowPrivilegeEscalation to true.

  4. Known Issues and Limitations for the MarkLogic Server Docker image can be viewed at Known Issues and Limitations.

  5. Path-based routing and Ingress features are only supported with MarkLogic 11.1 and higher.