marklogic-1.1.2

Release 1.1.2

Version 1.1.2 of the Helm chart for MarkLogic Server fixes a bug that prevents an upgrade from 1.0.x to 1.1.1 because of the StatefulSet naming convention change introduced in version 1.1.1.

A new parameter called useLegacyHostnames was added to the values file to allow upgrade from version 1.0.x. It defaults to false but when upgrading from version 1.0.x to 1.1.2 or later, this parameter must be set to true.

Because there are limitations to the length of fully-qualified hostnames in certificates, version 1.1.2 of the Helm chart provides feedback if the configured hostnames are more than 64 characters. If the generated hostnames are greater than 64 characters an error will be thrown and the upgrade will fail.

A new parameter called allowLongHostnames was added to the values file to allow overriding this behavior. This defaults to false but can be set to true if hostnames greater than 64 characters are acceptable for the target deployment.

marklogic-1.1.1

Release 1.1.1

WARNING: Because the StatefulSet naming convention has changed in 1.1, upgrading from version 1.0 of the MarkLogic Helm chart to 1.1 will cause the name of the StatefulSet to change and therefore, the original StatefulSet will be deleted and a new one will be created. This is equivalent to deploying a completely new MarkLogic cluster. The original persistent volumes will NOT be deleted so any data associated with the original MarkLogic StatefulSet can be recovered from the original persistent volumes if needed.

UPGRADING: To upgrade an existing MarkLogic cluster created from version 1.0 of the Helm chart, backup the existing cluster, upgrade the Helm chart to 1.1, and restore the backup to the new cluster. Once the system has been verified, the old persistent volumes can be deleted.

MarkLogic Server is a multi-model database that has both NoSQL and trusted enterprise data management capabilities.

Patch release 1.1.1 of the MarkLogic Helm Chart.

Bugfixes:

1. Fix for updating the existing cluster from HTTP to HTTPS.
2. Addressed the issue causing bootstrap host to become unresponsive in PodInitializing state post-restart.

marklogic-1.1.0

Release 1.1.0

WARNING: Because the StatefulSet naming convention has changed in 1.1, upgrading from version 1.0 of the MarkLogic Helm chart to 1.1 will cause the name of the StatefulSet to change and therefore, the original StatefulSet will be deleted and a new one will be created. This is equivalent to deploying a completely new MarkLogic cluster. The original persistent volumes will NOT be deleted so any data associated with the original MarkLogic StatefulSet can be recovered from the original persistent volumes if needed.

UPGRADING: To upgrade an existing MarkLogic cluster created from version 1.0 of the Helm chart, backup the existing cluster, upgrade the Helm chart to 1.1, and restore the backup to the new cluster. Once the system has been verified, the old persistent volumes can be deleted.

This minor release provides the following enhancements:

• Default App Servers can now be configured with HTTPS.
• Add Pod Topology Spread Constraints feature.
• HugesPages can now be configured in the Marklogic pods' resources.
• LoadBalancer HAProxy is now using the LTS release HAProxy 2.9.4.
• FluentBit is now using the version 2.2.2.
• The Helm chart now comes with the latest MarkLogic version available 11.1.0.

marklogic-1.0.2

Patch release 1.0.2 of the MarkLogic Helm Chart.

Bugfixes:

1. MarkLogic containers will never be marked as ready when the Security DB is not available
2. Special character '$' not accepted for admin password when used as Docker secrets
3. Additional volumes are not created with the right owner
4. Update 3rd party images to resolve severity vulnerabilities

marklogic-1.0.1

Patch release 1.0.1 of the MarkLogic Helm Chart.

Bugfixes:

1. Fixed a race condition in the post-start hook that caused the pods to fail to start when running on macOS on Apple silicon.

marklogic-1.0.0

This is the first release of the MarkLogic Helm Chart for Kubernetes. With this chart, MarkLogic clusters can easily be created and managed in Kubernetes.

See the MarkLogic on Kubernetes documentation for complete details.

marklogic-1.0.0-rc3

MarkLogic Server is a multi-model database that has both NoSQL and trusted enterprise data management capabilities.

marklogic-1.0.0-rc2

MarkLogic Server is a multi-model database that has both NoSQL and trusted enterprise data management capabilities.

marklogic-1.0.0-rc1

MarkLogic Server is a multi-model database that has both NoSQL and trusted enterprise data management capabilities.

1.0.0 EA2

MarkLogic Kubernetes EA2

This is the second Early Access (EA) release of the MarkLogic Helm Chart for Kubernetes. This Helm chart can be used to easily stand up MarkLogic clusters as StatefulSets along with the required Kubernetes Services for accessing MarkLogic.

Minimum MarkLogic Docker image version: 10.0-9.5-centos-1.0.0
Minimum Kubernetes version: 1.21

Known Issues and Limitations

1. This release is for development use only
2. Upgrades are not supported for EA releases
3. Full regression testing is still in progress and can not be guaranteed to be completed until the generally available release