Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/CustomResources.md
Original file line number Diff line number Diff line change
Expand Up @@ -193,7 +193,7 @@ the `Standalone` resource provides the following `Spec` configuration parameters

| Key | Type | Description |
| ---------- | ------- | ------------------------------------------------- |
| replicas | integer | The number of standalone replicas (defaults to 1) |
| replicas | integer | The number of standalone replicas (miminum of 1, which is the default) |


## SearchHeadCluster Resource Spec Parameters
Expand Down Expand Up @@ -263,7 +263,7 @@ the `IndexerCluster` resource provides the following `Spec` configuration parame

| Key | Type | Description |
| ---------- | ------- | ----------------------------------------------------- |
| replicas | integer | The number of indexer cluster members (defaults to 1) |
| replicas | integer | The number of indexer cluster members (minimum of 3, which is the default) |


## MonitoringConsole Resource Spec Parameters
Expand Down
2 changes: 1 addition & 1 deletion docs/Examples.md
Original file line number Diff line number Diff line change
Expand Up @@ -117,7 +117,7 @@ EOF
```
This will automatically configure a cluster, with a predetermined number of index cluster peers generated automatically based upon the replication_factor (RF) set. This example includes the `monitoringConsoleRef` parameter used to define a monitoring console pod.

NOTE: If you try to specify the number of `replicas` on an IndexerCluster CR less than the RF (as set on ClusterManager,) the Splunk Operator will always scale the number of peers to either the `replication_factor` for single site indexer clusters, or to the `origin` count in `site_replication_factor` for multi-site indexer clusters.
NOTE: If you try to specify the number of `replicas` on an IndexerCluster CR less than the RF (as set on ClusterManager,) the Splunk Operator will always scale the number of peers to either the `replication_factor` for single site indexer clusters, or to the `origin` count in `site_replication_factor` for multi-site indexer clusters. The minimum number of indexer cluster peers is 3.

After starting the cluster manager, indexer cluster peers, and monitoring console pods using the examples above, use the `kubectl get pods` command to verify your environment:
```
Expand Down
Loading