Solr

The Solr Helm chart allows you to deploy Solr, an open-source enterprise search platform, in your Kubernetes cluster. Solr is highly reliable and scalable, enabling you to build search solutions for various applications.

Prerequisites

• Kubernetes 1.19+
• Helm 3+

Add Helm Repository

To add the Helm repository, run the following commands:

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

Refer to the Helm Repository Documentation for additional details.

Install Helm Chart

To install the Solr Helm chart, use the following command:

helm install [RELEASE_NAME] zopdev/solr

Replace [RELEASE_NAME] with your desired release name. For example:

helm install my-solr zopdev/solr

For customized installation, provide a values.yaml file or override values during installation.

See Helm Install Documentation for additional details.

Uninstall Helm Chart

To uninstall the Solr Helm chart and remove all associated Kubernetes resources, run:

helm uninstall [RELEASE_NAME]

Example:

helm uninstall my-solr

Refer to Helm Uninstall Documentation for more information.

Configuration

Below are the configurable parameters for the Solr Helm chart:

You can override these values in a values.yaml file or via the command line.

Example values.yaml File

image: "solr:8.4"

resources:
  requests:
    memory: "1Gi"
    cpu: "200m"
  limits:
    memory: "4Gi"
    cpu: "2"

securityContext:
  runAsUser: 1001
  fsGroup: 1001

tlsSecretName: "solr-tls-secret"
host: "solr.example.com"
tlsHost: "secure-solr.example.com"

diskSize: "20Gi"

Apply the configuration file during installation:

helm install my-solr zopdev/solr -f values.yaml

Features

• High Security: The Helm chart allows you to configure secure environments using securityContext and TLS secrets.
• Persistent Storage: Persistent volumes ensure that Solr’s data is durable across deployments.
• Resource Control: Customizable CPU and memory resource allocations to optimize performance.
• Scalable Deployment: Easily scale resources or replicas for production use.

Advanced Usage

TLS Configuration

To enable secure communication, specify a Kubernetes secret containing TLS certificates in the tlsSecretName field. You can also set host and tlsHost for custom endpoints.

tlsSecretName: "solr-tls-secret"
host: "solr.example.com"
tlsHost: "secure-solr.example.com"

Persistent Volume Configuration

Customize the disk size and storage class to match your requirements:

diskSize: "50Gi"
storageClass: "fast-storage"

Pod Scheduling

nodeSelector, tolerations and affinity are passed straight through to the pod spec. All three are empty by default and render nothing, so leaving them unset changes nothing for an existing release.

Together they place the workload on a dedicated node pool — the nodeSelector picks the pool, the toleration gets past its taint:

nodeSelector:
  workload: stateful

tolerations:
  - key: workload
    operator: Equal
    value: stateful
    effect: NoSchedule

affinity takes a full Affinity object and is rendered verbatim.

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 : Hostname of the Solr StatefulSet service. Derived from release name.
• SOLR_PORT : Port number for Solr HTTP interface.Defaults at 8983.