You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The command deploys the solr-operator on the Kubernetes cluster with the default configuration. The [configuration](#chart-values) section lists the parameters that can be configured during installation.
49
+
The command deploys the solr-operator on the Kubernetes cluster with the default configuration.
50
+
The [configuration](#chart-values) section lists the parameters that can be configured during installation.
50
51
51
-
###Helm Version Differences
52
+
#### Namespaces
52
53
53
-
#### Helm 2
54
+
If you want to specify the namespace for the installation, use the `--namespace` flag.
55
+
All resources will be deployed to the given namespace.
54
56
55
-
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](../../config/crd/kustomization.yaml), and run `make manifests`
Note: Passing `false` and `""` to the `watchNamespaces` variable will both result in the operator watchting all namespaces in the Kube cluster.
73
+
74
+
### Managing CRDs
75
+
63
76
#### Helm 3
64
77
65
78
Helm 3 automatically runs CRDs in the /crds directory, no further action is needed.
66
79
80
+
If have solr operator installations in multiple namespaces that are managed separately, you will likely want to skip installing CRDs when installing the chart.
81
+
This can be done with the `--skip-crds` helm option.
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](../../config/crd/kustomization.yaml), and run `make manifests`
90
+
91
+
You will also need to update the install command to use the name flag, as shown below.
To uninstall/delete the `solr-operator` deployment:
@@ -85,12 +115,21 @@ The command removes all the Kubernetes components associated with the chart and
85
115
86
116
## Chart Values
87
117
118
+
### Configuring the Solr Operator
119
+
120
+
| Key | Type | Default | Description |
121
+
|-----|------|---------|-------------|
122
+
| watchNamespaces | string |`""`| A comma-separated list of namespaces that the solr operator should watch. If empty, the solr operator will watch all namespaces in the cluster. If set to `true`, this will be populated with the namespace that the operator is deployed to. |
123
+
| ingressBaseDomain | string |`""`| 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>`|
124
+
| useZkOperator | string |`"true"`| This option enables the use of provided Zookeeper instances for SolrClouds |
125
+
| useEtcdOperator | string |`"false"`| This option enables the use of provided Zetcd instances for SolrClouds |
126
+
88
127
### Running the Solr Operator
89
128
90
129
| Key | Type | Default | Description |
91
130
|-----|------|---------|-------------|
92
131
| image.repository | string |`"bloomberg/solr-operator"`| The repository of the Solr Operator image |
93
-
| image.tag | string |`"v0.2.1"`| The tag/version of the Solr Operator to run |
132
+
| image.tag | string |`"v0.2.5"`| The tag/version of the Solr Operator to run |
94
133
| image.pullPolicy | string |`"Always"`||
95
134
| fullnameOverride | string |`""`| A custom name for the Solr Operator Deployment |
96
135
| nameOverride | string |`""`||
@@ -99,11 +138,6 @@ The command removes all the Kubernetes components associated with the chart and
99
138
| resources.limits.memory | string |`"500Mi"`||
100
139
| resources.requests.cpu | string |`"100m"`||
101
140
| resources.requests.memory | string |`"100Mi"`||
102
-
103
-
### Configuring the Solr Operator
104
-
105
-
| Key | Type | Default | Description |
106
-
|-----|------|---------|-------------|
107
-
| ingressBaseDomain | string |`""`| 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>`|
108
-
| useZkOperator | string |`"true"`| This option enables the use of provided Zookeeper instances for SolrClouds |
109
-
| useEtcdOperator | string |`"false"`| This option enables the use of provided Zetcd instances for SolrClouds |
141
+
| rbac.create | boolean | true | Create the necessary RBAC rules, whether cluster-wide or namespaced, for the Solr Operator. |
142
+
| serviceAccount.create | boolean | true | Create a serviceAccount to be used for this operator. This serviceAccount will be given the permissions specified in the operator's RBAC rules. |
143
+
| serviceAccount.name | string | "" | If `serviceAccount.create` is set to `false`, the name of an existing serviceAccount in the target namespace **must** be provided to run the Solr Operator with. This serviceAccount with be given the operator's RBAC rules. |
0 commit comments