1. Proposed title of this feature request-  The capability to modify the primary shards for index template in OCP 4.X. 
2. What is the nature and description of the request?

 As per the documentation link[1], the number of primary shards for the index templates is equal to the number of Elasticsearch data nodes.

 [1]  https://docs.openshift.com/container-platform/4.4/logging/config/cluster-logging-elasticsearch.html

In the OCP 3.X, we were able to change the number of shards for the index template using the following article[2].

[2] https://access.redhat.com/solutions/4058621

How can we achieve this in the OCP 4.X?

  3. Why does the customer need this? (List the business requirements here)

The reason for trying to control primary shards is to manage the performance of the EFK stack.

 The customer is thinking of increasing client performance by creating data/client ES nodes, so setting node count to 5, the average shard size will get even smaller. Hence, the benefits made by creating data/client nodes will be lost due to further data fragmentation.

4. List any affected packages or components.

• OCP 4.x logging