Learn how to deploy Progress MarkLogic Server on a Kubernetes cluster in seven quick steps.
Setting up a database on Kubernetes might sound complex, but with the right tools and approach, it can be surprisingly straightforward. In this blog post, we'll show you just how easy it is to deploy a powerful database solution like Progress MarkLogic Server on a Kubernetes cluster.
Read on to explore the steps, tools and best practices that make this process efficient and accessible. Whether you're new to Kubernetes or an experienced user, you'll discover the simplicity and flexibility of containerizing your database, enabling you to unlock the full potential of MarkLogic Server in a modern, containerized environment.
We'll start by discussing the MarkLogic Docker image and MarkLogic Helm chart—relevant elements for setting up your MarkLogic cluster configuration in Kubernetes. After that, we'll guide you through the process of setting up a MarkLogic Server cluster locally in your Kubernetes environment. For setting up a cluster locally in EKS for production, refer to the MarkLogic Documentation.
The MarkLogic Docker image facilitates the swift deployment of MarkLogic Docker containers. This purpose-built image is designed to enhance your experience in creating and managing MarkLogic clusters in Kubernetes. By leveraging Docker to encapsulate applications, developers gain a straightforward method to write, package and deploy applications with ease. These applications can then be deployed anywhere, whether in the cloud or on premises.
Key benefits to the MarkLogic Docker image include:
Incorporate the MarkLogic Server Docker image into your Kubernetes cluster setup, and witness a more seamless blend of speed, flexibility and enhanced security, all in one place.
Helm simplifies the deployment process by providing package repositories and search capabilities. The MarkLogic Helm chart streamlines the creation and management of MarkLogic clusters in Kubernetes, offering a new level of flexibility and cross-cloud compatibility. At the time of writing, the Helm chart has been thoroughly tested on Amazon EKS and Azure AKS, facilitating reliability across these cloud platforms. One of the significant advantages of using Helm for MarkLogic deployments is its cloud-agnostic nature. Whether you're on AWS, Azure or another Kubernetes-enabled cloud provider, the Helm chart provides a consistent interface for managing MarkLogic clusters.
Before we dive into MarkLogic and Kubernetes, you'll need some essential tools:
Start minikube using the following command, referencing Docker as the hypervisor to be used:
Then, pull the latest MarkLogic Server image from Docker Hub into minikube by running the following command:
This step helps you ensures check that your minikube cluster can use the MarkLogic image. You may want to ensure confirm minikube is up and running by, running the Kubernetes command line tool, KubeCTL:
Add the MarkLogic Helm repository to your local environment:
To help secure your MarkLogic cluster, create a Kubernetes secret for custom admin credentials. Replace the placeholders with your desired values in the following command:
With the most recent release of the MarkLogic Helm chart, users gain access to a powerful tool for orchestrating MarkLogic clusters. The Helm chart simplifies the process by allowing users to configure the cluster size, security settings and other essential parameters through a straightforward configuration file. Check out our documentation for a full list of Helm Chart Parameters.
values.yaml file to configure your MarkLogic Server installation. Here's a simple example configuration for a three-node MarkLogic cluster:
Make sure to adjust the replicaCount and resource allocation to meet your requirements, setting it to any other odd number to avoid the split brain problem.
Check that the .yaml file is in your current directory, then install the MarkLogic Helm chart using the values.yaml file you created:
"my-release" can be any name of choice.
Verify the installation of the helm chart by running:
The installation may take a couple minutes to start each of the nodes.
You're almost done! To access your MarkLogic Server from localhost, you'll need to port forward requests:
Port forwarding essentially opens a tunnel between the pod and your laptop so you can connect to your pod or cluster.
Congratulations! You've successfully set up MarkLogic on Kubernetes locally. Now you're ready to explore your MarkLogic Cluster at http://localhost:8001. Remember, to sign in, you will need to enter the username and password selected in your Kubernetes secret from Step 5.
In the image below, you can see that three nodes have been created into a single cluster. At the top of the image, it shows that you are viewing the my-release-marklogic-0 node.
This is a great way to experiment, develop and test your MarkLogic applications before scaling them in production. As you become more comfortable with this setup, you can explore more advanced configurations and optimizations to tailor your MarkLogic cluster to your specific needs.
For more information on how to build upon this demo and prepare for scaling MarkLogic in production with Kubernetes, check out our MarkLogic Server on Kubernetes documentation.
Mitch joined the Product Management team at MarkLogic in 2021. He is responsible for developer tools, including client APIs, connectors, and integrators.
Mitch holds a Master’s Degree in Information Systems and an MBA from the University of Utah.
Let our experts teach you how to use Sitefinity's best-in-class features to deliver compelling digital experiences.Learn More
Subscribe to get all the news, info and tutorials you need to build better business apps and sites
You can also ask us not to share your Personal Information to third parties here: Do Not Sell or Share My Info
We see that you have already chosen to receive marketing materials from us. If you wish to change this at any time you may do so by clicking here.
Thank you for your continued interest in Progress. Based on either your previous activity on our websites or our ongoing relationship, we will keep you updated on our products, solutions, services, company news and events. If you decide that you want to be removed from our mailing lists at any time, you can change your contact preferences by clicking here.