Skip to main content
helm chart · solrcloud

SolrCloud

Helm chart for deploying Apache SolrCloud datastore

Latest version
v0.0.4
Chart type
Data source
Requires
Helm 3+

Install

Add the zop.dev chart repository, then install solrcloud into your cluster.

helm repo add zopdev https://helm.zop.dev
helm repo update
helm install my-solrcloud zopdev/solrcloud --version v0.0.4

This Helm chart deploys Apache SolrCloud on Kubernetes, providing a highly available, distributed search platform. SolrCloud is built on Apache Solr and offers features like distributed indexing, automatic sharding, and fault tolerance.


Prerequisites

  • Kubernetes 1.19+
  • Helm 3.0+
  • kubectl configured to communicate with your cluster
  • Solr Operator installed in the cluster (automatically installed as a dependency)

Dependencies

Before installing the chart, you need to download the required dependencies. Run the following command in the chart directory:

Terminal window
helm dependency build

This command will:

  1. Read the dependencies from Chart.yaml
  2. Download the required charts (Solr Operator) from the specified repositories
  3. Store them in the charts/ directory
  4. Create or update the Chart.lock file with the exact versions

If you encounter any issues with the dependencies, you can try:

Terminal window
helm dependency update # Updates dependencies to the latest versions

This chart requires the following dependencies to be installed:

Solr Operator

  • Chart: solr-operator
  • Version: 0.0.1
  • Repository: https://helm.zop.dev
  • Purpose: Manages the SolrCloud cluster lifecycle, including scaling, updates, and maintenance operations

To install this dependency automatically, ensure the following in your values.yaml:

Terminal window
solr-operator:
enabled: true
# Additional Solr Operator configuration...

The dependency will be automatically installed when you deploy the SolrCloud chart. You can customize its configuration through the respective section in your values.yaml file.


Add Helm Repository

Add the Helm repository by running:

Terminal window
helm repo add zopdev https://helm.zop.dev
helm repo update

For more details, see the Helm Repository Documentation.


Install Helm Chart

To deploy the SolrCloud Helm chart, use the following command:

Terminal window
helm install [RELEASE_NAME] zopdev/solrcloud

Replace [RELEASE_NAME] with your desired release name. Example:

Terminal window
helm install my-solrcloud zopdev/solrcloud

You can override default values during installation by providing a values.yaml file.

Refer to the Helm Install Documentation for further details.


Uninstall Helm Chart

To remove the SolrCloud Helm chart and associated resources, run:

Terminal window
helm uninstall [RELEASE_NAME]

Example:

Terminal window
helm uninstall my-solrcloud

Check the Helm Uninstall Documentation for more information.


Configuration

The SolrCloud Helm chart includes several configuration options to tailor the deployment to your needs. Below is a summary of the key configurations:

InputTypeDescriptionDefault
versionstringVersion of Solr to deploy."8.11"
resources.requests.cpustringMinimum CPU resources required by each Solr pod."500m"
resources.requests.memorystringMinimum memory resources required by each Solr pod."500Mi"
resources.limits.cpustringMaximum CPU resources each Solr pod can use."1000m"
resources.limits.memorystringMaximum memory resources each Solr pod can use."1500Mi"
diskSizestringSize of the persistent volume for Solr data storage."20Gi"
solr-operator.versionstringVersion of the Solr Operator to deploy."v0.9.0"
solr-operator.resources.requests.cpustringMinimum CPU resources for the Solr Operator."100m"
solr-operator.resources.requests.memorystringMinimum memory resources for the Solr Operator."128Mi"
solr-operator.resources.limits.cpustringMaximum CPU resources for the Solr Operator."200m"
solr-operator.resources.limits.memorystringMaximum memory resources for the Solr Operator."256Mi"

Example values.yaml

Terminal window
version: "8.11"
resources:
requests:
cpu: "500m"
memory: "500Mi"
limits:
cpu: "1000m"
memory: "1500Mi"
diskSize : "20Gi"
solr-operator:
version : "v0.9.0"
resources:
requests:
cpu: "100m"
memory: "128Mi"
limits:
cpu: "200m"
memory: "256Mi"

Features

  • Deploys a fully configured SolrCloud cluster
  • Automatic Zookeeper ensemble management
  • Persistent storage for Solr data
  • Basic authentication enabled by default
  • Pod disruption budget for high availability
  • Automatic scaling with pod vacate/populate
  • Managed update strategy
  • Customizable resource limits and requests
  • Automatic Solr Operator deployment

Architecture

The SolrCloud deployment includes:

  • SolrCloud cluster with configurable resources
  • Zookeeper ensemble (3 replicas by default)
  • Persistent volume claims for data storage
  • Pod disruption budget for high availability
  • Solr Operator for cluster management
  • Basic authentication security
  • Configurable update and scaling strategies

Contributing

We welcome contributions to improve this Helm chart. Please refer to the CONTRIBUTING.md file for contribution guidelines.


Code of Conduct

To maintain a healthy and collaborative community, please adhere to our Code of Conduct.


License

This project is licensed under the LICENSE. Please review it for terms of use.


Connection Config

  • SOLR_HOST : Headless service name for the SolrCloud StatefulSet.
  • SOLR_PORT : Port for accessing Solr HTTP interface.Defaults at 8983.
  • SOLR_USER : Username for Solr authentication.

See it fire on your bill.

Connect an account read-only. The first findings land in minutes.

472 rule families across 353 resource types on 22 platforms. Every threshold, metric, and IAM action is documented on these pages before you grant anything.

472 rule families documented
353 resource types covered
read-only default access level
Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·