tree: 7c27562cf9d7e180e910b9ac558f7fba5950882b [path history] [tgz]
  1. crds/
  2. templates/
  3. .helmignore
  4. Chart.yaml
  5. README.md
  6. values.yaml
helm/solr-operator/README.md

solr-operator

A Helm chart for the Solr Operator.

Installing the Chart

To install the chart with the release name test:

$ helm install test .

The command deploys the solr-operator on the Kubernetes cluster with the default configuration. The configuration section lists the parameters that can be configured during installation.

NOTE: Since by default the useZkOperator option is set to True, you must have already installed the Zookeeper Operator in your kubernetes cluster. A helm chart is also available for it.

Helm Version Differences

Helm 2

If you are using Helm 2, CRDs are installed using the crd-install hook. Prior to installing, you'll need to uncomment the last two lines in kustomization.yaml, and run make manifests

You will also need to update the install command to use the name flag, as shown below.

$ helm install --name test .

Helm 3

Helm 3 automatically runs CRDs in the /crds directory, no further action is needed.

Uninstalling the Chart

To uninstall/delete the solr-operator deployment:

Helm 3

$ helm uninstall test

Helm 2

$ helm delete test

The command removes all the Kubernetes components associated with the chart and deletes the release.

Chart Values

Running the Solr Operator

KeyTypeDefaultDescription
image.repositorystring"bloomberg/solr-operator"The repository of the Solr Operator image
image.tagstring"v0.2.1"The tag/version of the Solr Operator to run
image.pullPolicystring"Always"
fullnameOverridestring""A custom name for the Solr Operator Deployment
nameOverridestring""
replicaCountint1The number of Solr Operator pods to run
resources.limits.cpustring"400m"
resources.limits.memorystring"500Mi"
resources.requests.cpustring"100m"
resources.requests.memorystring"100Mi"

Configuring the Solr Operator

KeyTypeDefaultDescription
ingressBaseDomainstring""If you have a base domain that points to your ingress controllers for this kubernetes cluster, you can provide this. SolrClouds will then begin to use ingresses that utilize this base domain. E.g. solrcloud-test.<base.domain>
useZkOperatorstring"true"This option enables the use of provided Zookeeper instances for SolrClouds
useEtcdOperatorstring"false"This option enables the use of provided Zetcd instances for SolrClouds